Re: [DOCS] Links for upgraders

2014-02-12 Thread Tom Lane
Vik Fearing writes: > On 01/20/2014 08:35 AM, Tom Lane wrote: >> Why didn't you follow the existing style for the major-version links? >> That is, a pattern like >> However, if you are upgrading from a version earlier than 9.0.6, >> see . > I believe to have addressed your concerns in this new pa

[DOCS] archive_command vs recovery_command paths

2014-02-12 Thread Craig Ringer
Hi folks Another point of confusion I've been seeing a lot in users on Stack Overflow, dba.stackexchange.com, etc surrounds the meaning of paths given in archive_command and restore_command. Lots of people seem to assume that they are both relative to the master, and that the master will run the

Re: [DOCS] PATCH: Warn users about tablespace abuse data loss risk

2014-02-12 Thread Craig Ringer
On 02/12/2014 02:35 PM, Ian Lawrence Barwick wrote: > And taking a look at the page in question I see this prominent example: > > CREATE TABLESPACE fastspace LOCATION '/mnt/sda1/postgresql/data'; Here's an updated patch, adopting your wording for the first par and tweaking the example. -- C

Re: [DOCS] Links for upgraders

2014-02-12 Thread Joshua D. Drake
On 02/12/2014 03:40 PM, Tom Lane wrote: Peter Eisentraut writes: I think it would be even better to link directly to the migration notes, not to the top-level section of the release notes. I suggest to add a link target like Migration to Version 9.2.4 and then link to that. I

Re: [DOCS] Links for upgraders

2014-02-12 Thread Tom Lane
Peter Eisentraut writes: > I think it would be even better to link directly to the migration notes, > not to the top-level section of the release notes. I suggest to add a > link target like > >Migration to Version 9.2.4 > and then link to that. I experimented with this and didn't reall

Re: [DOCS] [HACKERS] Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)

2014-02-12 Thread Tom Lane
Peter Eisentraut writes: > On 2/8/14, 4:41 PM, Tom Lane wrote: >> + Release notes for all versions of PostgreSQL can be found on-line at >> + http://www.postgresql.org/docs/devel/static/release.html > Should be "current" instead of "devel"? >> + >> + In a distribution file set, release notes fo

Re: [DOCS] make vs. gmake

2014-02-12 Thread Bruce Momjian
On Fri, Jan 31, 2014 at 12:28:15PM -0500, Bruce Momjian wrote: > On Fri, Jul 26, 2013 at 01:49:32PM -0400, Bruce Momjian wrote: > > FYI, our source code build docs suggest 'gmake' in a number of places > > while 'make' would be used on other platforms. Should we change these > > to just say 'make

Re: [DOCS] [HACKERS] Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)

2014-02-12 Thread Peter Eisentraut
On 2/8/14, 4:41 PM, Tom Lane wrote: > diff --git a/HISTORY b/HISTORY > index ...360c7f6 . > *** a/HISTORY > --- b/HISTORY > *** > *** 0 > --- 1,6 > + Release notes for all versions of PostgreSQL can be found on-line at > + http://www.postgresql.org/docs/devel/static/release.ht

Re: [DOCS] [pgadmin-hackers] Ways to improve PgAdmin III SQL context help

2014-02-12 Thread Dave Page
Hi On Tue, Feb 11, 2014 at 5:33 PM, J.F. Oster wrote: > Hello All! > > Currently when I press F1 in the SQL Query window, PgAdmin III looks > for first token of selected (or whole) text, recognizes most of SQL > commands and tries to open corresponding help page. > > I tried to extend that list w