Re: BUG #11829: pgcrypto doc bug

From: Marko Kreen <markokr(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: jeff(dot)janes(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #11829: pgcrypto doc bug
Date: 2014-11-03 15:36:15
Message-ID: 20141103153615.GA23006@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Oct 30, 2014 at 04:50:44PM -0400, Tom Lane wrote:
> jeff(dot)janes(at)gmail(dot)com writes:
> > pgp_sym_encrypt is documented to have an enable-session-key option.
>
> > But that option does not seem to exist, and as far as I can tell it never
> > has existed.
>
> > jjanes=# select pgp_sym_encrypt('foo','bar','enable-session-key=1');
> > ERROR: Illegal argument to function
>
> A look at set_arg() suggests that the spelling of that option is really
> "sess-key" ... Marko, is that correct?

Yes.

> I also notice that there are a bunch of undocumented options with
> names beginning "expect-". Should those be documented, and if so
> could we get some text for that?

They are mainly meant for regtests, to see if final message structure
is what is expected. I don't see much value for users.

--
marko

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-11-03 15:47:38 Re: BUG #11829: pgcrypto doc bug
Previous Message Tom Lane 2014-11-01 17:19:12 Re: [BUGS] ltree::text not immutable?