>
> ...omissis...
>
> yes, it's for contrib modules. but you can access it via SHOW so maybe it
> makes sense to include it in pg_settings as well. Not for now but for the
> future maybe...
I agree: it could be a useful feature.
giampaolo
>
>
> Joachim
>
> --
> Joachim Wieland
> Giampaolo,
>
> On Sun, Jun 18, 2006 at 01:26:21AM +0200, Giampaolo Tomassoni wrote:
> > Or... Can I put a custom variable in pgsql.conf?
>
> Like that you mean?
>
>
> custom_variable_classes = 'identify'# list of custom variable
> classnames
> identify.id = 42
>
>
>
>
> templ
Giampaolo,
On Sun, Jun 18, 2006 at 01:26:21AM +0200, Giampaolo Tomassoni wrote:
> Or... Can I put a custom variable in pgsql.conf?
Like that you mean?
custom_variable_classes = 'identify'# list of custom variable classnames
identify.id = 42
template1=# show identify.id;
identif
> I assume by 'univocal' you mean unequivocal.
Yes, sorry about that: I'm writing italish...
> Can you set it up in a table per server? or in a file? or would you
> rather use a guuid?
A per-server table will probably be my way.
> And how is this to be made available?
Well, a function would
> ...omissis...
>
> Perhaps inet_server_addr() and inet_server_port() would answer. These
> aren't super-useful on local connections, however.
No, infact. Mine are local cons...
> How "immutable" do you want it to be exactly? The system_identifier
> embedded in pg_control might be interesting
