We would have more than no-time-at-all to test it and fix any breakage.
Just to start close to home, do you really trust either psql or pg_dump
to be completely free of standard_conforming_strings issues? How about
JDBC or ODBC? Python drivers? PLs?
Oh, yeah. I was just thinking about
On Fri, Jan 29, 2010 at 5:44 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Bruce Momjian br...@momjian.us writes:
Well, since I asked in April of 2009, at the beginning of the cycle, 6
years after the introduction of the variable, and we still are not doing
it, then let's stop pretending we will ever
It's a good question if that still makes sense with Hot Standby.
Perhaps we should redefine smart shutdown in standby mode to shut down
as soon as all read-only connections have died.
It's clear that smart shutdown doesn't work while something is active.
Recovery is active and so we
On Fri, Jan 29, 2010 at 7:01 PM, Josh Berkus j...@agliodbs.com wrote:
It's a good question if that still makes sense with Hot Standby.
Perhaps we should redefine smart shutdown in standby mode to shut down
as soon as all read-only connections have died.
It's clear that smart shutdown doesn't
On Friday 29 January 2010 23:47:22 Bruce Momjian wrote:
Andres Freund wrote:
On Friday 29 January 2010 23:34:09 Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
I stand by the position that it's way too late in the cycle for
insufficiently-thought-out proposals for major
2010/1/29 Tom Lane t...@sss.pgh.pa.us:
Josh Berkus j...@agliodbs.com writes:
I stand by the position that it's way too late in the cycle for
insufficiently-thought-out proposals for major behavioral changes.
I don't see how announcing this earlier in the dev cycle would help, at
all.
We
=?ISO-8859-1?Q?C=E9dric_Villemain?= cedric.villemain.deb...@gmail.com writes:
2010/1/29 Tom Lane t...@sss.pgh.pa.us:
We would have more than no-time-at-all to test it and fix any breakage.
Just to start close to home, do you really trust either psql or pg_dump
to be completely free of
An actual plan here might look like let's flip it before 9.1alpha1
so we can get some alpha testing cycles on it ...
Hey, let's flip it in 9.1 CF 1, so that we can have some alpha testing
cycles on it.
;-)
--Josh Berkus
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
Tim Bunce wrote:
This is an updated version of the third of the patches to be
split out from the former 'plperl feature patch 1'.
It includes changes following discussions with Tom Lane and others.
Changes in this patch:
- Added plperl.on_perl_init GUC for DBA use (PGC_SIGHUP)
SPI
On Mon, Jan 25, 2010 at 12:53, Tim Bunce tim.bu...@pobox.com wrote:
- Added the 'warnings' pragma to the list of modules to load into Safe.
So plperl functions can now use warnings; - added test for that.
*yay*
- Added 'use 5.008001;' to plc_perlboot.pl as a run-time check to
complement
On Sat, Jan 30, 2010 at 9:01 AM, Josh Berkus j...@agliodbs.com wrote:
I don't think it's clear, or intuitive for users. In SR, recovery is
*never* done, so smart shutdown never completes (even if the master is
shut down, when I tested it).
If you specify the trigger_file parameter in the
Hi there,
I made available test data I used on
http://www.sai.msu.su/~megera/wiki/2009-07-27,
so anyone can reproduce my results. You can download data
http://www.sai.msu.su/~megera/postgres/files/links2.sql.gz, it's big (580Mb)
Regards,
Oleg
On 01/29/2010 09:01 PM, Tom Lane wrote:
Maybe. We concluded in the April 2009 thread that
standard_conforming_strings = ON had gotten little or no field testing,
and I don't see any strong reason to hope that it's gotten much more
since then. It would be rather surprising if there *aren't* any
Michael Glaesemann michael.glaesem...@myyearbook.com writes:
We came across a regexp that takes very much longer than expected.
I poked into this a little bit. What seems to be happening is that the
use of non-greedy quantifiers plus backreferences turns off most of the
optimization that the
101 - 114 of 114 matches
Mail list logo
