Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Store 2PC GID in commit/abort WAL recs for logicaldecoding - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pgsql: Store 2PC GID in commit/abort WAL recs for logicaldecoding
Date
Msg-id 20180615191218.py3ti2fzxlysxf7h@alvherre.pgsql
Whole thread Raw
In response to Re: pgsql: Store 2PC GID in commit/abort WAL recs for logical decoding  (Nikhil Sontakke <nikhils@2ndquadrant.com>)
Responses Re: pgsql: Store 2PC GID in commit/abort WAL recs for logicaldecoding
List pgsql-hackers
Tree view 
By the way, why do we need to strlen() the target buffer when strlcpy
already reports the length?  (You could argue that there is a difference
if the string is truncated ... but surely we don't care about that case)
I propose the attached.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Store 2PC GID in commit/abort WAL recs for logicaldecoding
Next
From: Joe Conway
Date:
Subject: Re: missing toast table for pg_policy