Skip site navigation (1) Skip section navigation (2)

Re: Async Commit, v21 (now: v22)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org, "Bruce Momjian" <bruce(at)momjian(dot)us>
Subject: Re: Async Commit, v21 (now: v22)
Date: 2007-07-23 22:59:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> Thanks for reading. Updated version in new patch.

What was the reasoning for basing walwriter.c on autovacuum (which needs
to be able to execute transactions) rather than bgwriter (which does
not)?  The shutdown logic in particular seems all wrong; you can't have
a process connected to shared memory that is going to outlive the

			regards, tom lane

In response to


pgsql-patches by date

Next:From: Simon RiggsDate: 2007-07-23 23:22:55
Subject: Re: Async Commit, v21 (now: v22)
Previous:From: Simon RiggsDate: 2007-07-23 22:11:55
Subject: Re: Reviewing new index types (was Re: [PATCHES] Updatedbitmap indexpatch)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group