Bruce Momjian writes:
> Works for me, though, is there no interest in keeping the SGML files in
> the git tree and just not building them as docs?
Yeah, I thought about that alternative, but I'm not sure I see the
percentage. It'd bloat the tarballs compared to removing them,
and for what?
On Wed, Aug 8, 2018 at 09:53:42PM +0700, Chris Travers wrote:
> It seems to me that this would still provide enough historical
> info for just about any ordinary interest. We could discuss ways
> of making a complete release-note archive available somewhere,
> if "go dig in the
On Wed, Aug 8, 2018 at 8:57 AM, Tom Lane wrote:
> > Secondly
> > dblink_is_busy must be first called to make dblink_error_message returns
> an
> > error message. (Tested on 9.6.9)
>
> Meh. I see what you're getting at here, I think, but that seems like a
> completely wrong/misleading statement
=?utf-8?q?PG_Doc_comments_form?= writes:
> The following documentation comment has been logged on the website:
> Documentation says:
> Return Value
> Returns last error message, or an empty string if there has been no error in
> this connection.
> Which is invalid.
> Actually it returns 'OK'
On Mon, Aug 6, 2018, 05:57 Tom Lane wrote:
> We've been around on this before, I know, but I got annoyed about it
> again while waiting around for test builds of the back-branch
> documentation. I think that we need some policy about maintaining
> back-branch release notes that's not "keep
The following documentation comment has been logged on the website:
Page:
https://www.postgresql.org/docs/10/static/contrib-dblink-error-message.html
Description:
Documentation says:
Return Value
Returns last error message, or an empty string if there has been no error in
this connection.
