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

Re: [HACKERS] Full page writes improvement, code update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>, "Koichi Suzuki" <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Full page writes improvement, code update
Date: 2007-04-24 18:19:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> Well, as a PG hacker I find the name wal_fullpage_optimization quite
> baffling and I think our general user base will find it even more so.
> Now that I have Koichi's explanation of the problem, I vote for simply
> slaving this to the PITR settings and not having a separate option at
> all.

The way to not have a separate option is to not need one, by having the
feature not cost anything extra in the first place.  Andreas and I have
made the point repeatedly about how to do that.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Gregory StarkDate: 2007-04-24 18:23:00
Subject: Re: UNION with more than 2 branches
Previous:From: Josh BerkusDate: 2007-04-24 17:50:05
Subject: Re: [HACKERS] Email signature in release announcement posting

pgsql-patches by date

Next:From: Heikki LinnakangasDate: 2007-04-24 20:04:03
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k o b j ect
Previous:From: Josh BerkusDate: 2007-04-24 15:31:42
Subject: Re: [HACKERS] Full page writes improvement, code update

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