Re: Patch to document base64 encoding

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Patch to document base64 encoding
Date: 2020-01-09 07:27:28
Message-ID: alpine.DEB.2.21.2001090825550.7789@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Karl,

> Another option would be to use "bytes bytea".

> (The current patch uses "string bytea".)
> This would probably also require some re-wording throughout.

> Please let me know your preference.

I like it, but this is only my own limited opinion, and I'm not a native
English speaker.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2020-01-09 07:47:59 Re: [Logical Replication] TRAP: FailedAssertion("rel->rd_rel->relreplident == REPLICA_IDENTITY_DEFAULT || rel->rd_rel->relreplident == REPLICA_IDENTITY_FULL || rel->rd_rel->relreplident == REPLICA_IDENTITY_INDEX"
Previous Message Neha Sharma 2020-01-09 07:20:16 Re: [Logical Replication] TRAP: FailedAssertion("rel->rd_rel->relreplident == REPLICA_IDENTITY_DEFAULT || rel->rd_rel->relreplident == REPLICA_IDENTITY_FULL || rel->rd_rel->relreplident == REPLICA_IDENTITY_INDEX"