[COMMITTERS] pgsql-server/src/test/regress Tag: REL7_4_STAB ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 20:50:52 Modified files: src/test/regress: Tag: REL7_4_STABLE parallel_schedule Log message: Run stats test separately, not as part of a parallel group, to avoid possibl

[COMMITTERS] pgsql-server/src/test/regress parallel_schedule

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 20:50:33 Modified files: src/test/regress: parallel_schedule Log message: Run stats test separately, not as part of a parallel group, to avoid possible failures due to s

[COMMITTERS] pgsql-server/src backend/commands/async.c back ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 20:45:26 Modified files: src/backend/commands: async.c src/backend/libpq: pqsignal.c src/backend/main: main.c src/backend/port: sysv_sema.c sysv_shmem.c

[COMMITTERS] pgsql-server/src/backend/libpq pqsignal.c

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 20:46:58 Modified files: src/backend/libpq: pqsignal.c Log message: Pgindent win32 signal code. ---(end of broadcast)--- TIP 4:

[COMMITTERS] pgsql-server/src backend/postmaster/pgstat.c b ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 18:59:54 Modified files: src/backend/postmaster: pgstat.c postmaster.c src/backend/storage/ipc: ipci.c pmsignal.c src/backend/tcop: postgres.c src/backend/utils

[COMMITTERS] pgsql-server/src backend/postmaster/pgstat.c b ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 18:54:58 Modified files: src/backend/postmaster: pgstat.c postmaster.c src/backend/storage/ipc: ipci.c pmsignal.c src/backend/tcop: postgres.c src/backend/utils

[COMMITTERS] pgsql-server/src backend/access/transam/xact.c ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 18:51:56 Modified files: src/backend/access/transam: xact.c src/backend/postmaster: pgstat.c postmaster.c src/backend/storage/ipc: ipci.c pmsignal.c src/backend

[COMMITTERS] pgsql-server/doc TODO

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 18:38:42 Modified files: doc: TODO Log message: Add Name: > * -Add checks for fclose() failure (Tom) ---(end of broadcast)

[COMMITTERS] pgsql-server/doc TODO

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 18:38:10 Modified files: doc: TODO Log message: Done: > * -Add checks for fclose() failure (Tom) ---(end of broadcast)

[COMMITTERS] pgsql-server/src backend/access/transam/slru.c ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 18:35:32 Modified files: src/backend/access/transam: slru.c xlog.c src/backend/commands: copy.c user.c src/backend/postmaster: postmaster.c src/backend/storage/

[COMMITTERS] pgsql-server/doc/src/sgml libpq.sgml

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 18:13:21 Modified files: doc/src/sgml : libpq.sgml Log message: The attached patch clarifies (or, rather, makes explicit) to readers how to handle memory management fo

Re: [COMMITTERS] pgsql-server/src backend/storage/buffer/bufmgr ...

Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> Not necessarily --- it could be out-of-disk-space, on at least some > >> filesystems. More to the point, the important thing is not to commit a > > > I assume the operating system is already allocating file syste

Re: [COMMITTERS] pgsql-server/src backend/storage/buffer/bufmgr ...

Bruce Momjian <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Not necessarily --- it could be out-of-disk-space, on at least some >> filesystems. More to the point, the important thing is not to commit a > I assume the operating system is already allocating file system space > during the write,

Re: [COMMITTERS] pgsql-server/src backend/storage/buffer/bufmgr ...

Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> As I've said before, I think we need to find a way to stop using sync() > >> altogether --- we have to move to fsync or O_SYNC and variants. sync > >> has simply got the wrong API. > > > If sync failes (kernel to

Re: [COMMITTERS] pgsql-server/src backend/storage/buffer/bufmgr ...

Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> As I've said before, I think we need to find a way to stop using sync() > >> altogether --- we have to move to fsync or O_SYNC and variants. sync > >> has simply got the wrong API. > > > If sync failes (kernel to

Re: [COMMITTERS] pgsql-server/src backend/storage/buffer/bufmgr ...

Bruce Momjian <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> As I've said before, I think we need to find a way to stop using sync() >> altogether --- we have to move to fsync or O_SYNC and variants. sync >> has simply got the wrong API. > If sync failes (kernel to disk write failes) we have a

Re: [COMMITTERS] pgsql-server/src backend/storage/buffer/bufmgr ...

Jan Wieck wrote: > Tom Lane wrote: > > > Jan Wieck <[EMAIL PROTECTED]> writes: > > >> The whole point of the bgwriter is to give responsetimes a better > >> variance, I never claimed that it will improve performance. > > > > I want to use it to improve reliability, by getting rid of our > > dep

Re: [COMMITTERS] pgsql-server/src backend/storage/buffer/bufmgr ...

Tom Lane wrote: > Jan Wieck <[EMAIL PROTECTED]> writes: > > So far nobody bothered to make any other proposal how to cause the > > kernel to actually do some writing at all. A lot of people babble about > > fsync(), fdatasync() and fadvise and whatnot. A week ago I posted the > > proposal for th

Re: [COMMITTERS] pgsql-server/src backend/storage/buffer/bufmgr ...

Jan Wieck wrote: > Tom Lane wrote: > > > [EMAIL PROTECTED] (Jan Wieck) writes: > >>Added GUC variable bgwriter_flush_method controlling the action > >>done by the background writer between writing dirty blocks and > >>napping. > > > >>none (default) no action > >>sync

[COMMITTERS] pgsql-server/src/backend/access/transam Tag: R ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 15:16:41 Modified files: src/backend/access/transam: Tag: REL7_3_STABLE varsup.c Log message: Repair incorrect order of operations in GetNewTransactionId(). We must com

[COMMITTERS] pgsql-server/src/backend/access/transam varsup.c

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 15:16:00 Modified files: src/backend/access/transam: varsup.c Log message: Repair incorrect order of operations in GetNewTransactionId(). We must complete ExtendCLOG()

[COMMITTERS] pgsql-server/src/backend/access/transam Tag: R ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 15:16:23 Modified files: src/backend/access/transam: Tag: REL7_4_STABLE varsup.c Log message: Repair incorrect order of operations in GetNewTransactionId(). We must com

[COMMITTERS] pgsql-server/doc TODO

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 14:32:09 Modified files: doc: TODO Log message: Added: > * Dump large object comments in custom dump format ---(end of bro

[COMMITTERS] pgsql-server/doc/src/sgml/ref execute.sgml pre ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 13:26:31 Modified files: doc/src/sgml/ref: execute.sgml prepare.sgml Log message: Add usage examples for PREPARE and EXECUTE. Original patch from Gavin Sherry, editorial

[COMMITTERS] pgsql-server/contrib/ltree Tag: REL7_4_STABLE ...

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 11:08:58 Modified files: contrib/ltree : Tag: REL7_4_STABLE README.ltree Log message: Docs fix from Kris Jurka <[EMAIL PROTECTED]> ---(end of broadca

[COMMITTERS] pgsql-server/contrib/ltree README.ltree

CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/01/26 11:08:52 Modified files: contrib/ltree : README.ltree Log message: Docs fix from Kris Jurka <[EMAIL PROTECTED]> ---(end of broadcast)