PgSql

[HACKERS] Did we really want to force an initdb in beta2?
Because that's the consequences of fooling with pg_control. I committed the PG_CONTROL_VERSION bump that was missing from the patch Robert committed last night, but I wonder whether we shouldn't revert the whole thing instead. It's not apparent to me that what it bought is worth forcing beta testers to initdb. ... 3 Jun 2010 11:08

Comments on Exclusion Constraints and relateddatatypes
David Fetter wrote: On Mon, Mar 22, 2010 at 04:04:16PM -0300, Alvaro Herrera wrote: David Fetter wrote: diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 9881ff4..9313112 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -7134,7 +7134,7... 2 Jun 2010 22:00

[HACKERS] current value support
Hi all, Please see attached a patch that finishes the support for currval. All the structure was in place in GTM but there was still one missing call in sequence.c when calling the function. Now it is possible to get current values for sequences in the whole cluster. Regards, -- Michael Paquier NIPPON ... 2 Jun 2010 22:00

ALTER TABLE .... make constraint DEFERRABLE
Simon Riggs wrote: Deferrable unique constraints seem an interesting feature, though I have either some questions or some issues, not sure which. I don't seem to be able to find any way to do an ALTER TABLE that adds this new capability to an existing table. I was able to do it: test=> create... 3 Jun 2010 11:08

Idea for getting rid of VACUUM FREEZE on coldpages
Alvaro Herrera wrote: Excerpts from Robert Haas's message of mié jun 02 14:16:33 -0400 2010: We could, but I think we'd be better off just freezing at the time we mark the page PD_ALL_VISIBLE and then using the visibility map for both purposes. Keeping around the old xmin values after every tuple... 12 Jun 2010 12:39

recovery getting interrupted is not so unusual as it used to be
On 02/06/10 23:50, Robert Haas wrote: First, is it appropriate to set the control file state to DB_SHUTDOWNED_IN_RECOVERY even when we're in crash recovery (as opposed to archive recovery/SR)? My vote is no, but Heikki thought it might be OK. My logic on that is: If the database is known to be in goo... 2 Jun 2010 18:42

Allow wal_keep_segments to keep all segments
On Wed, Jun 2, 2010 at 3:20 PM, Bruce Momjian <bruce(a)momjian.us> wrote: Bruce Momjian wrote: Robert Haas wrote: On Sat, May 8, 2010 at 10:40 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: Bruce Momjian <bruce(a)momjian.us> writes: Uh, did we decide that 'wal_keep_segments' was the best name for thi... 3 Jun 2010 17:54

[HACKERS] Allow wal_keep_segments to keep all segments
Bruce Momjian wrote: Robert Haas wrote: On Sat, May 8, 2010 at 10:40 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: Bruce Momjian <bruce(a)momjian.us> writes: Uh, did we decide that 'wal_keep_segments' was the best name for this GUC setting? ?I know we shipped beta1 using that name. ... 2 Jun 2010 16:29

"caught_up" status in walsender
On 02/06/10 21:44, Tom Lane wrote: In conjunction with that, I think there's a logic bug in XLogSend; it ought to be changed like so: /* if we went beyond SendRqstPtr, back off */ if (XLByteLT(SendRqstPtr, endptr)) + { endptr = SendRqstPtr; + *caughtup = true; + } In the current co... 3 Jun 2010 12:17

[HACKERS] "caught_up" status in walsender
I wrote: I'm still inclined to apply the part of Simon's patch that adds a transmit timestamp to each SR send chunk. That would actually be completely unused by the slave given my proposal above, but I think that it is an important step to take to future-proof the SR protocol against possible changes in... 2 Jun 2010 15:23