[PATCHES] pgstat EXEC_BACKEND

For application to HEAD, following community review. Corrects a typo, introduces missing variables, and rearranges the initialization of stats process under EXEC_BACKEND. [A cleaner, rationalized approach to stat/backend/SSDataBase child processes under EXEC_BACKEND is on my TODO list. However

Re: [PATCHES] contrib/xml2 function name change and minor bitrot

On Sun, 2004-03-07 at 17:54 -0500, Tom Lane wrote: > Neil Conway <[EMAIL PROTECTED]> writes: > > A few comments on the module: > > > - can you include some licensing information? "Distributed under the > > same terms as PostgreSQL, Copyright ..." should be sufficient unless > > you'd prefer anot

Re: [PATCHES] Update tests & memory leak fix

Got the diff -c now, thanks. --- Lee Kindness wrote: > Sorry guys, last diff wasn't a context one! "diff -c" attached this time > round... > > L. > > - Original Message - > From: Lee Kindness > To: [EMAIL PROTECTED

Re: [PATCHES] ECPG: Update tests & memory leak fix

I need a context diff, diff -c. --- Lee Kindness wrote: > See attached diff which corrects a per-thread memory leak in libecpg and changes the > thread test program to create a user defined number of threads. Also attached

Re: [PATCHES] contrib/xml2 function name change and minor bitrot fix

Patch applied by Neil (thanks). Thanks. --- John Gray wrote: > Hi, > > I've done a bit of testing now and it seems that both sets of XML > functions will coexist in the same database (they both load OK and I can > use fun

Re: [PATCHES] Alter table patch

Rod Taylor <[EMAIL PROTECTED]> writes: > This patch seems to have fallen off of Bruces "To be applied" list > without being applied. Could I get a status report? > http://archives.postgresql.org/pgsql-patches/2003-11/msg00222.php That was the one that did a wholesale revision of the ALTER TABLE i

Re: [PATCHES] Alter table patch

Rod Taylor wrote: > On Mon, 2004-03-08 at 13:41, Tom Lane wrote: > > Rod Taylor <[EMAIL PROTECTED]> writes: > > > This patch seems to have fallen off of Bruces "To be applied" list > > > without being applied. Could I get a status report? > > > > > http://archives.postgresql.org/pgsql-patches/2003

[PATCHES] libpq v2 protocol error: COPY FROM STDIN, PQputCopyEnd()

This fixes a protocol violation and disconnect when 7.4.x libpq is talking to a v2 protocol (<=7.3.x) server. The client does COPY FROM STDIN, uses the new call PQputCopyData(), then ends the copy using PQputCopyEnd(), and gets back the odd message: FATAL: Socket co

Re: [PATCHES] log_line_info

Andrew Dunstan wrote: > > I think this is now ready for application, unless someone objects. > > Since the last patch I posted, I have done the following: > > . changed the escapes to lower case, as Peter prefers. This is also in > line with what Apache does, which is the nearest equivalent I c

Re: [PATCHES] log_line_info

Oh, I also renamed it to "log_line_prefix", which was one of your suggestions. And I also updated some of the documentation phrasing. I also marked the TODO item as completed. Thanks. --- Andrew Dunstan wrote: > > I thin

Re: [PATCHES] canonicalize_path: initdb.c -> port/path.c

Patch applied. Thanks. --- Claudio Natoli wrote: > > For application to HEAD. > > The win32 port backend will require the functionality provided by > canonicalize_path. Patch moves it from initdb.c to port/path.c. > > -

Re: [PATCHES] PostgreSQL: libpq, win32 build

This builds a debug version of the DLL's along with the non-debug version. Patch applied. Thanks. --- David Turner wrote: > Hi > > > > release build uses the cl flags "/MD /D NDEBUG". Usually the debug > > > build has a

Re: [PATCHES] "ALSO" keyword to "CREATE RULE" patch

Patch applied. Thanks. --- Fabien COELHO wrote: > > > Shoot me the patch again and I will put in the the queue. Thanks. > > Please find attached (again) the patch I sent. It is against 7.4.1. > If necessary, I can redo