From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Thom Brown <thom@linux.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: pg_dump locking info
Date: Sun, 15 Aug 2010 17:13:53 -0400
Message-ID: <5448.1281906833@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTimitNSWoh9RmiUWX20e4oqNcTvFts6xGABqe_Sz@mail.gmail.com>
References: <AANLkTi=B3x8MQQvd_xyncArJ9CLPT3cSu8-UjVNZVopr@mail.gmail.com>
<AANLkTimfssadCt+9w9-iqHpbcKYm8=yH5vYGAJDsW2TA@mail.gmail.com>
<AANLkTimitNSWoh9RmiUWX20e4oqNcTvFts6xGABqe_Sz@mail.gmail.com>
Robert Haas <robertmhaas@gmail.com> writes:
> On Sun, Aug 15, 2010 at 5:29 AM, Thom Brown <thom@linux.com> wrote:
>> And whilst I was perusing the docs, I also noticed this on
>> http://www.postgresql.org/docs/current/static/backup.html
>>
>> "Each has its own strengths and weaknesses. Each is discussed in turn below."
>>
>> That sentence is at the bottom of the page. It would make sense in a
>> PDF, but might be a confusing in section-by-section HTML
>> documentation.
> I don't find it so, but I suppose if it's a big deal we could change
> it to read "in the following sections".
Yeah, that's what I was thinking of doing in response to Thom's gripe.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, thom@linux.com
Subject: Re: pg_dump locking info
In-Reply-To: <5448.1281906833@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox