Re: aclitem binary encoding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joseph Koshakow <koshy44(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: aclitem binary encoding
Date: 2023-07-21 14:58:21
Message-ID: 828616.1689951501@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Joseph Koshakow <koshy44(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2023-07-21 15:28:48 Re: invalid value for parameter "default_text_search_config": "public.pg"
Previous Message Adrian Klaver 2023-07-21 14:49:49 Re: invalid value for parameter "default_text_search_config": "public.pg"