[PATCHES] Path to enable a module to change the stack_base_ptr

2005-10-02 Thread Thomas Hallgren
Here is a patch that will enable a module to change the stack_base_ptr temporarilly during a call. A background discussion can be found here: http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg64586.html Regards, Thomas Hallgren Index: src/backend/tcop/postgres.c

Re: [PATCHES] Making pgxs builds work with a relocated installation

2005-10-02 Thread Dave Page
-Original Message- From: Tom Lane[EMAIL PROTECTED] Sent: 01/10/05 17:55:42 To: Dave Pagedpage@vale-housing.co.uk Cc: pgman@candle.pha.pa.uspgman@candle.pha.pa.us, [EMAIL PROTECTED][EMAIL PROTECTED], pgsql-patches@postgresql.orgpgsql-patches@postgresql.org Subject: Re: Making pgxs

Re: [PATCHES] Proposed patch for sequence-renaming problems

2005-10-02 Thread Michael Paesold
Tom Lane wrote: Here's an updated version of the patch. There's now just one nextval() function, taking regclass, and backwards compatibility is handled through an implicit text-to-regclass cast. Existing dumps will not see any behavioral changes because nextval('foo') will be dumped as

[PATCHES] Make 2PC error messages match docs

2005-10-02 Thread Steve Woodcock
Hi, This makes the error messages for PREPARE TRANSACTION, COMMIT PREPARED etc. match the docs, which talk about transaction identifier not gid or global transaction identifier. Regards, Steve Woodcock Index: src/backend/access/transam/twophase.c

Re: [PATCHES] Path to enable a module to change the stack_base_ptr

2005-10-02 Thread Tom Lane
Thomas Hallgren [EMAIL PROTECTED] writes: Here is a patch that will enable a module to change the stack_base_ptr temporarilly during a call. I'm not really in favor of this ... I think you are trying to make the backend do something that will never work reliably. If we were to try to support

Re: [PATCHES] External Sort timing debug statements

2005-10-02 Thread Simon Riggs
On Sun, 2005-10-02 at 19:43 +0100, Simon Riggs wrote: The following patch implements a fairly light set of timing statements aimed at understanding external sort performance. There is no attempt to alter the algorithms. Minor update of patch, use this version please. Best Regards, Simon

[PATCHES] database file compatibility patch

2005-10-02 Thread Qingqing Zhou
This patches checks MAXIMUM_ALIGNOF and endian to make sure that the database file used is compatible with the server version. We use SHORT_ALIGNOF, INT_ALIGNOF, DOUBLE_ALIGNOF and MAXIMUM_ALIGNOF (which is just the largest of these) to align columns within a row (see att_align()) or rows within

[PATCHES] External Sort timing debug statements

2005-10-02 Thread Simon Riggs
The following patch implements a fairly light set of timing statements aimed at understanding external sort performance. There is no attempt to alter the algorithms. Each major point in the algorithms is marked as shown in this example: postgres=# set debug_sort=true; SET postgres=# explain

Re: [PATCHES] Path to enable a module to change the stack_base_ptr

2005-10-02 Thread Thomas Hallgren
Tom Lane wrote: Thomas Hallgren [EMAIL PROTECTED] writes: Here is a patch that will enable a module to change the stack_base_ptr temporarilly during a call. I'm not really in favor of this ... I think you are trying to make the backend do something that will never work reliably. If

[PATCHES] Docs for PITR and full_page_writes interaction

2005-10-02 Thread Simon Riggs
Some additional doc changes based around compression of page images in WAL and the interaction of the new full_page_writes parameter with PITR. The too-small WAL first sect1 has been merged with the one following sect1 for clarity. Some minor comments have been made in the WAL config section

Re: [PATCHES] SQL/XML publishing function experimental patch II

2005-10-02 Thread David Fetter
On Wed, Sep 28, 2005 at 04:30:54PM +0200, Pavel Stehule wrote: Hello base type changed to text, better registration xmlagg function Regards Pavel Stehule Now with some slightly improved documentation, works vs. CVS tip as of this writing. Cheers, D -- David Fetter [EMAIL PROTECTED]

Re: [PATCHES] database file compatibility patch

2005-10-02 Thread Tom Lane
Qingqing Zhou [EMAIL PROTECTED] writes: This patches checks MAXIMUM_ALIGNOF and endian to make sure that the database file used is compatible with the server version. I missed seeing this patch in my inbox, so wrote and applied my own version earlier today. Sorry for the missed communication

Re: [PATCHES] database file compatibility patch

2005-10-02 Thread Qingqing Zhou
Tom Lane [EMAIL PROTECTED] wrote There's not much need to check endianness explicitly, since the pg_control_version check will surely fail if there's an endianness discrepancy (not to mention the other checks on pg_control fields). Oh, right. So for the same reason, is it safe to remove

Re: [PATCHES] database file compatibility patch

2005-10-02 Thread Tom Lane
Qingqing Zhou [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] wrote There's not much need to check endianness explicitly, since the pg_control_version check will surely fail if there's an endianness discrepancy (not to mention the other checks on pg_control fields). Oh, right. So for

[PATCHES] cleanup log_disconnections()

2005-10-02 Thread Qingqing Zhou
Trivial patch to cleanup log_disconnections() function. Regards, Qingqing --- Index: postgres.c === RCS file: /projects/cvsroot/pgsql/src/backend/tcop/postgres.c,v retrieving revision 1.463 diff -u -r1.463 postgres.c ---