| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: pg_dump locking info |
| Date: | 2010-08-15 21:13:53 |
| Message-ID: | 5448.1281906833@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sun, Aug 15, 2010 at 5:29 AM, Thom Brown <thom(at)linux(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-15 23:05:43 | Re: pg_dump locking info |
| Previous Message | Robert Haas | 2010-08-15 21:01:30 | Re: pg_dump locking info |