| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Brar Piening <brar(at)gmx(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Minor documentation error regarding streaming replication protocol |
| Date: | 2020-12-02 20:16:30 |
| Message-ID: | 20201202201630.GD20285@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 1, 2020 at 10:16:31AM -0800, Jeff Davis wrote:
> On Thu, 2020-10-08 at 23:17 -0400, Bruce Momjian wrote:
> > As I said before, it is more raw bytes, but
> > we
> > don't have an SQL data type for that.
>
> Sorry to jump in to this thread late.
>
> Can't we just set both "filename" and "content" to be BYTEA, but then
> set the format code to 1 (indicating binary)?
>
> For clients that do look at the descriptor, they are more likely to get
> it right; and for clients that don't look at the descriptor, there will
> be no change.
Yes, we could, but I thought the format code was not something we set at
this level. Looking at byteasend() it is true it just sends the bytes.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-12-02 20:26:22 | Re: Add docs stub for recovery.conf |
| Previous Message | Fabien COELHO | 2020-12-02 20:03:28 | Re: Add table access method as an option to pgbench |