| From: | Vick Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Hiding data in postgresql |
| Date: | 2010-05-25 19:48:04 |
| Message-ID: | AANLkTil9ROMY_0hacI_ZAo_QlV4Oa5sWwLOfdLPmQQvz@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, May 25, 2010 at 11:30 AM, Hector Beyers <hqbeyers(at)gmail(dot)com> wrote:
> Maybe to save populate a table with 1000 rows, but the meta-data only knows
> of about 500 of them? Only on an export of a dump can you find the data
> again.
Well, here's your flaw: If you expect the data dumper to be able to
export the rows, then the system must know that the rows/tables are
there, and thus cannot be "hidden" for any definition of hidden. To
find them, you just do the work that the dumper would do.
Ie, you seem to want to be able to write files that postgres doesn't
know are there, and that I don't believe you can do.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Coventry | 2010-05-25 19:55:11 | Re: export data to excel |
| Previous Message | Hector Beyers | 2010-05-25 19:39:44 | Fwd: Hiding data in postgresql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicolas Barbier | 2010-05-25 19:53:30 | Re: Exposing the Xact commit order to the user |
| Previous Message | Hector Beyers | 2010-05-25 19:39:44 | Fwd: Hiding data in postgresql |