Re: BUG #17325: Unexpected streaming replication protocol bytes for IDENTIFY_SYSTEM command

From: Greg Rychlewski <greg(dot)rychlewski(at)gmail(dot)com>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17325: Unexpected streaming replication protocol bytes for IDENTIFY_SYSTEM command
Date: 2021-12-08 13:06:02
Message-ID: CAKemG7VMzWbgVV-nsJP5mmi2pSEcv+OLcOrPWEx9ZhB2OJ9u6w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Apologies, this is a false alarm. The oid returned for the datatype is int4
but since this is a simple query the actual value is a string. I didn't
read the doc correctly the first time.

On Tue, Dec 7, 2021 at 9:46 PM PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 17325
> Logged by: Greg Rychlewski
> Email address: greg(dot)rychlewski(at)gmail(dot)com
> PostgreSQL version: 13.0
> Operating system: x86_64-apple-darwin18.7.0
> Description:
>
> Hi,
>
> I ran the following command and captured the packets with wire shark:
>
> psql "dbname=postgres replication=database" -c "IDENTIFY_SYSTEM;"
>
> The timeline ID returned from psql is displayed as 1. Based on the protocol
> docs, I was expecting the packets to correspond to an int32 value of 1, but
> I am seeing them coming as the string "1". I see following (values are
> hexadecimal):
>
> 00 00 00 01 for the length
> 31 for the value
>
> Thanks,
> Greg
>
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitry Dolgov 2021-12-08 13:46:01 Re: BUG #17326: Postgres crashed when pg_reload_conf() with ssl certificate parameters
Previous Message PG Bug reporting form 2021-12-08 11:23:35 BUG #17327: Postgres server does not correctly emit error for max_slot_wal_keep_size being breached