Re: libpq options

2017-11-28 Thread Şahap Aşçı 
I think this solves the consistency issue that i am talking about. Well, i
am just looking from documentation user point of view.

If it's developer only option and shouldn't be documented then maybe adding
a 'IDENTIFY_SYSTEM' parameter to pg_receivexlog is more appropriate.
like this pg_receivexlog ...  --identify-system






On Sat, Nov 25, 2017 at 1:05 PM, Michael Paquier 
wrote:

> On Wed, Nov 22, 2017 at 11:36 PM, Michael Paquier
>  wrote:
> > Yeah, it is mainly a developer option which is why I guess it is not
> > documented. Like you, I think it should be added as part of the
> > connection parameter, and mentioned it a couple of days back:
> > https://www.postgresql.org/message-id/CAB7nPqQAtKfG3H%
> 2BuK11JNivtJtZYE9yVCrPuejRMjp8tUDe0nQ%40mail.gmail.com
>
> Attached is a patch as an attempt to bring together the best of both
> worlds. The idea is to move the description of how the connection
> parameter replication works from the replication protocol page into
> the section of libpq dedicated to connection parameters, and add links
> between both sections.
>
> Thoughts?
> --
> Michael
>



-- 
Şahap Aşçı

Re: libpq options

2017-11-28 Thread Michael Paquier 
On Tue, Nov 28, 2017 at 5:00 PM, Şahap Aşçı  wrote:
> I think this solves the consistency issue that i am talking about. Well, i am 
> just looking from documentation user point of view.

Thanks. Input is always welcome. I have added an entry in the commit
fest app so as this is not lost:
https://commitfest.postgresql.org/16/1387/
-- 
Michael

Re: [DOCS] Docbook 5.x

2017-11-28 Thread Peter Eisentraut 
On 11/25/17 00:50, Alexander Lakhin wrote:
> Please, consider applying the attached patch. It produces the same
> INSTALL and is much better in the following aspects.
> 
> 1. All the INSTALL content is placed in two files (installation.sgml and
> installation-single.xsl) instead of three (installation.sgml,
> standalone-install.xml, standalone-profile.xsl).
> 2. There are no unreadable and untranslatable (in context) constructions
> such as
> 
>   the
> PL/Python
> documentation
> 
> (Sometimes translators need to replace larger fragments.)
> 3. It uses only XSLT (which we use already), no xi:include.
> 4. It doesn't generate complete postgres.sgml to process only the
> installation section.

What is the standalonetext attribute?  I don't see that in the DTD.
Wouldn't that fail validation?

Also, the makefile fragments need to be written differently.  You can't
use pipes; that would not catch any errors.

-- 
Peter Eisentraut  http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: [DOCS] Docbook 5.x

2017-11-28 Thread Alexander Lakhin 

Hello Peter,
28.11.2017 19:02, Peter Eisentraut wrote:


What is the standalonetext attribute?  I don't see that in the DTD.
Wouldn't that fail validation?

I've added it to postgres.sgml as allowed by DocBook standard:
http://www.sagehill.net/docbookxsl/AddProfileAtt.html
+


Also, the makefile fragments need to be written differently.  You can't
use pipes; that would not catch any errors.


I believe, that the last xsltproc will fail in case of error in previous 
command(s) as it will not get valid xml. For example, if sed failed with 
error, I get:

-:1: parser error : Document is empty


Best regards,
--
Alexander Lakhin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company