From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joseph Koshakow <koshy44@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: aclitem binary encoding
Date: Fri, 21 Jul 2023 10:58:21 -0400
Message-ID: <828616.1689951501@sss.pgh.pa.us> (raw)
In-Reply-To: <CAAvxfHdpbCjJ6VO+BmJgMVA1yu50xBAEGw2NWaNnug-W0rBHCg@mail.gmail.com>
References: <CAAvxfHdpbCjJ6VO+BmJgMVA1yu50xBAEGw2NWaNnug-W0rBHCg@mail.gmail.com>
Joseph Koshakow <koshy44@gmail.com> writes:
> Is this an intentional decision to not support a binary encoding for
> aclitem types? Or is it just a lack of a feature?
I think it's at least somewhat intentional, to have a core type
that has no binary I/O so that that case can be tested. In any
event, a binary representation probably wouldn't be terribly
useful, as it'd contain role OIDs that wouldn't reliably transport
from one system to the next, and also privilege bitmasks that
we sometimes redefine.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, koshy44@gmail.com
Subject: Re: aclitem binary encoding
In-Reply-To: <828616.1689951501@sss.pgh.pa.us>
References: <CAAvxfHdpbCjJ6VO+BmJgMVA1yu50xBAEGw2NWaNnug-W0rBHCg@mail.gmail.com> <828616.1689951501@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox