Re: Getting the type Oid in a CREATE TYPE output function

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Weslee Bilodeau" <weslee(dot)bilodeau(at)hypermediasystems(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Getting the type Oid in a CREATE TYPE output function
Date: 2006-10-16 13:35:33
Message-ID: e51f66da0610160635y7b4d2631vca8a24c2d9b4a306@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/12/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Weslee Bilodeau <weslee(dot)bilodeau(at)hypermediasystems(dot)com> writes:
> > It works perfectly so long as I used the same key for all my custom
> > types. When I want a different key for each type though (so for example,
> > encrypt credit cards with one key, addresses with another, etc) I need a
> > way to tell them apart.
>
> [ shrug... ] Seems like you should be putting the key ID into the
> stored encrypted datums, then.

The PGP functions happen to do it already - pgp_key_id().

--
marko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-10-16 14:00:13 Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8
Previous Message Merlin Moncure 2006-10-16 13:31:58 Re: more anti-postgresql FUD