From: | Peter Hunsberger <peter(dot)hunsberger(at)gmail(dot)com> |
---|---|
To: | Hector Beyers <hqbeyers(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Hiding data in postgresql |
Date: | 2010-05-24 20:29:27 |
Message-ID: | AANLkTikRhizGVeucux_V6VAfqysD9YaAv4ATuuXK71H3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Mon, May 24, 2010 at 3:24 PM, Hector Beyers <hqbeyers(at)gmail(dot)com> wrote:
> Dear Peter,
> can you elaborate on what you mean by storing 'this' in the index. Are you
> referring to the function that is applied over the data?
> How would you be able to see the result with a dump?
Yes, you would the function to create the index, something like:
create index gunk on tbl1 ( hidefunc( a, b, c ) )
The data created in this index might be viewable in a database dump by
simple inspection with something like an editor. How meaningful it
might be is another question...
--
Peter Hunsberger
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-05-24 20:32:16 | Re: Hiding data in postgresql |
Previous Message | Hector Beyers | 2010-05-24 20:24:27 | Re: Hiding data in postgresql |
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-05-24 20:32:16 | Re: Hiding data in postgresql |
Previous Message | Hector Beyers | 2010-05-24 20:24:27 | Re: Hiding data in postgresql |