Jae Adams writes:
> The document that I'm looking at this here. I apologize for not sending
> the link. I had thought that the URL would be included automatically
> through the link on the documentation website.
> -- https://www.postgresql.org/docs/11/ecpg-sql-set-autocommit.html (shows
> the c
PG Doc comments form writes:
> I have a c++ library built with libpq.so, and I am trying to run the
> statements "SET AUTOCOMMIT TO ON" and "SET AUTOCOMMIT TO OFF". According to
> the docs, it looks like those statements are valid.
Uh ... exactly what documentation are you looking at?
PG hasn't
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/ecpg-commands.html
Description:
I have a c++ library built with libpq.so, and I am trying to run the
statements "SET AUTOCOMMIT TO ON" and "SET AUTOCOMMIT TO OFF". According to
the docs,
PG Doc comments form writes:
> In "Table 8.7. bytea Literal Escaped Octets", the backslash character should
> be escaped as '\\' or '\134', not '\' or '\\134'.
Yup, you're right, somebody had a brain fade there.
Thanks for noticing!
regards, tom lane
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/sql-createtrigger.html
Description:
The AFTER Statement-level Trigger runs into infinite execution when another
set of rows are affected for the same table through this trigger. Consider
t
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/sql-createtrigger.html
Description:
The behaviour is not clear for BEFORE Statement-level Trigger. This is
because transition tables cannot be used. So how does one get access to the
rows
On 07/02/2019 18:11, Jürgen Purtz wrote:
>>> @@ -152,15 +156,15 @@ postgres.txt: postgres.html
>>> postgres.pdf:
>>> $(error Invalid target; use postgres-A4.pdf or postgres-US.pdf as
>>> targets)
>>>
>>> -%-A4.fo: stylesheet-fo.xsl %.sgml $(ALLSGML)
>>> +%-A4.fo: stylesheet-fo.xsl %.sgml
>>>
