Re: optionally schema-qualified for table_name

2020-03-24 Thread Bruce Momjian
On Tue, Mar 24, 2020 at 09:35:25PM +0100, Peter Eisentraut wrote: > On 2020-03-23 02:27, Bruce Momjian wrote: > > On Sun, Mar 22, 2020 at 06:20:04PM -0400, Tom Lane wrote: > > > Bruce Momjian writes: > > > > On Sun, Mar 22, 2020 at 03:05:01PM -0400, Tom Lane wrote: > > > > > I don't really think

Re: optionally schema-qualified for table_name

2020-03-24 Thread Peter Eisentraut
On 2020-03-23 02:27, Bruce Momjian wrote: On Sun, Mar 22, 2020 at 06:20:04PM -0400, Tom Lane wrote: Bruce Momjian writes: On Sun, Mar 22, 2020 at 03:05:01PM -0400, Tom Lane wrote: I don't really think this is an improvement, mainly because that error message is inventing a notation that we

Re: terminology in example

2020-03-24 Thread Bruce Momjian
On Tue, Mar 24, 2020 at 03:57:25PM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/ddl-inherit.html > Description: > > In the example on this page: >

terminology in example

2020-03-24 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/ddl-inherit.html Description: In the example on this page: https://www.postgresql.org/docs/current/ddl-inherit.html the word 'altitude' should be replaced with 'elevation'.

Re: documentation pdf build fail (HEAD)

2020-03-24 Thread Tom Lane
Peter Eisentraut writes: > On 2020-03-24 15:31, Tom Lane wrote: >> The problem seems to be that cedffbdb8 >> introduced some broken table markup. I wonder why xmllint >> failed to catch it? > It's not a validity issue in the DocBook markup. The error comes from > FOP, which complains because

Re: documentation pdf build fail (HEAD)

2020-03-24 Thread Peter Eisentraut
On 2020-03-24 15:31, Tom Lane wrote: The problem seems to be that cedffbdb8 introduced some broken table markup. I wonder why xmllint failed to catch it? It's not a validity issue in the DocBook markup. The error comes from FOP, which complains because it requires the column count, but

Re: documentation pdf build fail (HEAD)

2020-03-24 Thread Tom Lane
Erikjan Rijkers writes: > I build the pdf (for HEAD) almost daily without problems, but at the > moment I get the error below. > I am not sure whether to blame my particular setup (debian stretch), or > whether there might be an error in the .sgml. The html files still > build OK. Yeah, I

Re: Examples required in || 5.10. Table Partitioning

2020-03-24 Thread Bruce Momjian
On Tue, Mar 24, 2020 at 12:36:14PM +0530, Tanay Purnaye wrote: > Hello Bruce, > > Apologies for late reply. > Thank you for acknowledging my email. > > If I have any doubts regarding partition,indixing or query tuning in feature > may I email you? No, I suggest you sent it to the appropriate

Re: documentation pdf build fail (HEAD)

2020-03-24 Thread Jürgen Purtz
Ubuntu 18.04: no crash, but possibly a side effect: [INFO] FOUserAgent - Rendered page #2685. [INFO] FOUserAgent - Rendered page #2686. [INFO] FOUserAgent - Rendered page #2687. [WARN] FOUserAgent - Destination: Unresolved ID reference "function-encode" found. [WARN] FOUserAgent - Destination:

documentation pdf build fail (HEAD)

2020-03-24 Thread Erikjan Rijkers
Hello, I build the pdf (for HEAD) almost daily without problems, but at the moment I get the error below. I am not sure whether to blame my particular setup (debian stretch), or whether there might be an error in the .sgml. The html files still build OK. If anyone has a suggestion on how

Re: Examples required in || 5.10. Table Partitioning

2020-03-24 Thread Tanay Purnaye
Hello Bruce, Apologies for late reply. Thank you for acknowledging my email. If I have any doubts regarding partition,indixing or query tuning in feature may I email you? Kind regards, Tanay On Sun, Mar 15, 2020, 1:12 AM Bruce Momjian wrote: > On Thu, Feb 6, 2020 at 12:23:46PM +, PG