Tom Lane wrote:
> Bruce Momjian writes:
> > -- Set escape environment for possible loading into version >= 8.2.
> > -- If variables are not supported, suppress error messages.
> > SET client_min_messages = panic;
> > SET log_min_messages = log;
> > SET log_min_error_statement =
I wrote:
> Per discussion among pgsql-packagers, we'll release 8.1.4 and updates in
> the back branches next week; tentative plan is tarballs wrapped Monday,
> public release Wednesday. Get those last-minute fixes in now ...
Upon further review, various people have time constraints that make this
Bruce Momjian writes:
> -- Set escape environment for possible loading into version >= 8.2.
> -- If variables are not supported, suppress error messages.
> SET client_min_messages = panic;
> SET log_min_messages = log;
> SET log_min_error_statement = panic;
> SE
pg_dump is designed to produce dumps that can be loaded into newer
PostgreSQL versions, and it can read from older database versions.
The new backslash escape warning and sql standard strings might cause
problems for people moving from older versions of PostgreSQL, because
pg_dump assumes identifi
Of course, that's an option for my case. Just wanted to know if this solution
could be useful for PostgreSQL in general. Mainly because I'll add some
triggers to check what maybe PostgreSQL should do itself but it's
unimplemented.
If that's not interesting or a proper solution for PostgreSQL I
On Fri, May 12, 2006 at 09:05:55PM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > Incidentally, is it necessary to load the DH parameters anew and
> > call DH_check for every connection?
>
> We could maybe improve on that on Unix, but not so easily on Windows.
> Given the ev
On Fri, May 12, 2006 at 08:38:07PM -0400, Bruce Momjian wrote:
> Is this like detecting of libpq is SSL-enabled? I see PQgetssl(). Do
> we need to add a libpq function to return true/false for threading?
> Slony requires a threaded libpq, so it could do the test to prevent
> wrong configurations
