Re: Hot standby and synchronous replication status

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot standby and synchronous replication status
Date: 2009-08-13 17:10:51
Message-ID: 4A84491B.4080405@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

All,

> The other reason is what I think Greg Smith was mentioning --
> simplifying the process of grabbing a usable PITR backup for novice
> users. That seems like it has merit.

While we're at this, can we add xlog_location as a file-location GUC?
It seems inconsistent that we're still requiring people to symlink the
pg_xlog in order to move that. Or is that already part of this set of
patches?

--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2009-08-13 17:17:44 Re: surprising trigger/foreign key interaction
Previous Message Pavel Stehule 2009-08-13 17:05:44 Re: Implementation of GROUPING SETS (T431: Extended grouping capabilities)