Re: COPY manual is ambiguous about column list

2019-12-19 Thread Pavlo Golub
On Thu, 19 Dec 2019 at 17:53, Bruce Momjian wrote: > > On Thu, Nov 28, 2019 at 02:53:03PM +0100, Pavlo Golub wrote: > > On Thu, 28 Nov 2019 at 10:47, Laurenz Albe wrote: > > > > > > On Wed, 2019-11-27 at 17:54 +, PG Doc comments form wrote: > > > >

Re: COPY manual is ambiguous about column list

2019-11-28 Thread Pavlo Golub
On Thu, 28 Nov 2019 at 10:47, Laurenz Albe wrote: > > On Wed, 2019-11-27 at 17:54 +, PG Doc comments form wrote: > > "If a list of columns is specified, COPY will only copy the data in the > > specified columns to or from the file. If there are any columns in the table > > that are not in the

Re: Authentication Methods page is broken on v11 and v12

2019-09-11 Thread Pavlo Golub
Oh, god. Sorry about that. :) Thanks for letting me know, Alvaro. On Wed, Sep 11, 2019, 17:05 Alvaro Herrera wrote: > On 2019-Sep-11, Pavlo Golub wrote: > > > Trying to view > > > > https://www.postgresql.org/docs/11/auth-methods.html > > https://www.postgresql

Authentication Methods page is broken on v11 and v12

2019-09-11 Thread Pavlo Golub
Trying to view https://www.postgresql.org/docs/11/auth-methods.html https://www.postgresql.org/docs/12/auth-methods.html https://www.postgresql.org/docs/current/auth-methods.html gives me an empty page. Previous versions are not affected.

Re: Bug reporting guidelines order of instructions

2019-01-23 Thread Pavlo Golub
t;>>> change the order of these and suggest the web form as the primary method, >>>> since that hands out bug ids? >>> >>> +1. >> >> +(many) > +1, esp. based on the progress of this thread[1] Yeap, good point! +1 from me > Jonathan > [1] > https://www.postgresql.org/message-id/flat/20190114221809.eymqah36d6uq5nir%40alap3.anarazel.de -- Best regards, Pavlo Golub

Re: `transaction_read_only` GUC undocumented

2019-01-22 Thread Pavlo Golub
Greetings, Michael. You wrote 23.01.2019, 8:14: > On Wed, Jan 23, 2019 at 01:07:31AM -0500, Tom Lane wrote: >> Michael Paquier writes: >>> transaction_read_only is listed in src/backend/utils/misc/guc.c, so we >>> could put a description close to default_transaction_read_only in >>> config.sgml,

Re: `transaction_read_only` GUC undocumented

2019-01-22 Thread Pavlo Golub
On Jan 23, 2019 02:25, Michael Paquier wrote:On Tue, Jan 22, 2019 at 01:26:40PM +0100, Pavlo Golub wrote: > I found that `transaction_read_only`GUC is undocumented. The only > place where it referenced is Hot Standby section > (https://www.postgresql.org/docs/current/hot-sta

`transaction_read_only` GUC undocumented

2019-01-22 Thread Pavlo Golub
Hello. I found that `transaction_read_only`GUC is undocumented. The only place where it referenced is Hot Standby section (https://www.postgresql.org/docs/current/hot-standby.html) Can we add description for this GUC, please?

Re: Updating the intro for packages - improve usability, reduce new user confusion

2018-12-05 Thread Pavlo Golub
Hello, Craig. You wrote: CR> TL;DR: It's time to update the docs to make package-based and CR> installer-based PostgreSQL the assumed environment our users are CR> working with. Or at least put it on an equal footing as a first-class CR> citizen, not relegate it to the dark corners of notes and a

Table 28.4. wait_event description typo

2018-05-30 Thread Pavlo Golub
Greetings, Pgsql-docs. On monitoring statistic page [1] we have typo. Table 28.4. wait_event description contains: ... ClientRead Waiting to read data from the client. ClientWrite Waiting to write data from the client. ... ^ It should state TO CLIENT. Thannk