| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: protecting prosrc (was Re: [GENERAL] USAGE on schema |
| Date: | 2002-12-02 21:24:31 |
| Message-ID: | 3DEBCF8F.8080902@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Robert Treat wrote:
> NOTE: redirecting to hackers
good idea!
> I think this would be a good idea, though there becomes a question of
> what type of performance hit comes into play when doing this. I suppose
> if you have an option whether to encrypt it or not that would help. One
> other thing is that it needs to be "decryptable" by owners and
> superusers.
For sure -- I would not propose doing this unless it was an optional thing.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2002-12-02 21:27:36 | Re: [SQL] CURRENT_TIMSTAMP |
| Previous Message | Christopher Kings-Lynne | 2002-12-02 21:17:18 | Re: protecting prosrc (was Re: [GENERAL] USAGE on schema allowed by |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-12-02 21:30:13 | Re: protecting prosrc (was Re: [GENERAL] USAGE on schema |
| Previous Message | Christopher Kings-Lynne | 2002-12-02 21:17:18 | Re: protecting prosrc (was Re: [GENERAL] USAGE on schema allowed by |