| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Change timeline field of IDENTIFY_SYSTEM to int8 |
| Date: | 2022-07-04 19:40:49 |
| Message-ID: | 8cd4a15e-f78f-aa09-7575-08efafe351c1@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 04.07.22 19:32, Tom Lane wrote:
> If the result of IDENTIFY_SYSTEM is always sent in text format, then
> I agree that this isn't very problematic. If there are any clients
> that fetch it in binary mode, though, this is absolutely a wire
> protocol break for them
The result rows of the replication commands are always sent in text format.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-07-04 20:54:04 | Re: pgsql: dshash: Add sequential scan support. |
| Previous Message | Peter Eisentraut | 2022-07-04 18:05:01 | pgsql: Refactor sending of RowDescription messages in replication proto |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-07-04 20:06:17 | Re: TAP output format in pg_regress |
| Previous Message | Alvaro Herrera | 2022-07-04 19:38:42 | Re: doc: BRIN indexes and autosummarize |