-
Notifications
You must be signed in to change notification settings - Fork 0
Configuration
no0p edited this page Oct 15, 2014
·
3 revisions
The plotpg extension adds a handle of GUCs to configure how plots will be drawn.
A grab bag of gnuplot directives directives are included based on a guess of which are most likely to be desired as permanent configurations.
| GUC | Description | Default |
|---|---|---|
| plotpg.terminal | The gnuplot set terminal command value. | "dumb" |
| plotpg.size | Gnuplot set size command value | "" |
| plotpg.title | Gnuplot set title command value | "" |
| plotpg.xlabel | Gnuplot set xlabel command value | "" |
| plotpg.ylabel | Gnuplot set ylabel command value | "" |
| plotpg.xrange | Gnuplot set xrange command value | "" |
| plotpg.yrange | Gnuplot set yrange command value | "" |
| plotpg.xtics | Gnuplot set xtics command value | "" |
| plotpg.ytics | Gnuplot set ytics command value | "" |
| plotpg.key | Gnuplot set key command value | "" |
| plotpg.border | Gnuplot set border command value | "" |
An example of setting a GUC, in this case the terminal to render svg, follows:
``` =# set plotpg.terminal='svg'; SET ```
### Developer GUCs
| GUC | Description | Default |
|---|---|---|
| plotpg.persist | plotpg will leave gnuplot script and output files in /tmp when set to 1. | 0 |
The plotpg files created:
| plotpg_<pg_backend_pid>.script | this is gnuplot script generated by the plot function. It will be executed by gnuplot. |
| plotpg_<pg_backend_pid>.data | This is the data file written by the plot command. The gnuplot script will reference this file when executing the plotting command. |
| plotpg_<pg_backend_pid>.output | This is where the results of the gnuplot script are stored. plotpg will read this file and return it to the client. |