I tried to add this to the documentation, config.sgml, but everything I
come up with sounds so long-winded that it would do more harm than good.
---
Jeff Davis wrote:
> On Thu, 2006-10-26 at 19:46 -0400, Tom Lane wrote:
> >
On Thu, 2006-10-26 at 19:46 -0400, Tom Lane wrote:
> Jeff Davis <[EMAIL PROTECTED]> writes:
> > You can set standard_conforming_strings in postgresql.conf at any time
> > and reload the config, changing the value for all active connections.
> > That means that if a client opens a connection, and yo
Jeff Davis <[EMAIL PROTECTED]> writes:
> You can set standard_conforming_strings in postgresql.conf at any time
> and reload the config, changing the value for all active connections.
> That means that if a client opens a connection, and you SIGHUP postgres,
> and then the client issues a PQescapeS
On Thu, 2006-10-26 at 16:19 -0700, Jeff Davis wrote:
> You can set standard_conforming_strings in postgresql.conf at any time
> and reload the config, changing the value for all active connections.
I should have mentioned, my email only applies to the upcoming 8.2
release.
Regards,
Jeff D
You can set standard_conforming_strings in postgresql.conf at any time
and reload the config, changing the value for all active connections.
That means that if a client opens a connection, and you SIGHUP postgres,
and then the client issues a PQescapeStringConn, the client will get an
incorrectly
