2012-07-17 06:32 keltezéssel, Alvaro Herrera írta:
Excerpts from Tom Lane's message of vie jul 13 18:23:31 -0400 2012:
Boszormenyi Zoltan z...@cybertec.at writes:
Try SET deadlock_timeout = 0;
Actually, when I try that I get
ERROR: 0 is outside the valid range for parameter deadlock_timeout
On Fri, Jul 20, 2012 at 01:39:34PM -0400, Alvaro Herrera wrote:
Excerpts from Noah Misch's message of mar jul 17 16:28:32 -0400 2012:
The foreign key tests, however, would benefit
from running under all three isolation levels. Let's control it per-spec
instead of repeating the entire
On 07/19/2012 10:32 AM, Andrew Dunstan wrote:
On 07/19/2012 10:12 AM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Wed, Jul 18, 2012 at 5:30 PM, Andrew Dunstan
and...@dunslane.net wrote:
Or we could provide an initdb flag which would set an upper bound on
shared_buffers, and
Am 20.07.12 01:40, schrieb Tom Lane:
RelationGetDescr(rel)-attrs[n]-attbyval
Thanks!
Now does 'Relation' refer to the whole table or only the columns that
are supposed to be scanned? So will RelationGetDescr(rel)-attrs[0] give
me the description of the first column relevant to the current
On Fri, Jul 20, 2012 at 03:39:33PM -0400, Robert Haas wrote:
On Fri, Jul 20, 2012 at 1:52 PM, Tom Lane t...@sss.pgh.pa.us wrote:
And with that too. The STRICT option is a fairly obvious security
hazard, but who's to say there are not others? I think it'd be easier
to make a case for
I have uploaded the patch for new option in pg_resetxlog at below location:
https://commitfest.postgresql.org/action/patch_view?id=897
This completes the implementation of Option-2 discussed in below mail.
Now I will work on Option-1 (1. To compute the value of max LSN in data pages
based
On Tue, Jul 17, 2012 at 06:56:50PM -0400, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Mon, Jul 16, 2012 at 3:18 PM, Tom Lane t...@sss.pgh.pa.us wrote:
BTW, while we are on the subject: hasn't this split completely
broken the statistics about backend-initiated writes?
