Prev: [HACKERS] Reason why set-value functions not allowed in GREATEST(), etc?
Next: Wire protocol docs
From: Bruce Momjian on 22 Feb 2010 13:08
Josh Berkus wrote:
>
> > Yeah, they basically have semantics specified by the SQL standard that
> > are not compatible with anything else in GUC land. They are more like
> > SET LOCAL settings, but again not quite.
>
> Mind you, transaction_isolation and transaction_read_only aren't
> documented anywhere in our docs *as settings*, even though they show up
> in pg_settings.
>
> Doc patch coming ...

What are we doing with this?

--
Bruce Momjian <bruce(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: [HACKERS] Reason why set-value functions not allowed in GREATEST(), etc?
Next: Wire protocol docs