| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <janwieck(at)Yahoo(dot)com> |
| Cc: | Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Unhappy thoughts about pg_dump and objects inherited from template1 |
| Date: | 2000-11-09 15:50:29 |
| Message-ID: | 6439.973785029@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Wieck <janwieck(at)Yahoo(dot)com> writes:
> For now we have oid's 1-16383 hardwired from the bki files.
> Some 16384-xxxxx get allocated by initdb after bootstrap, so
> we just need to bump the oid counter at the end of initdb (by
> some bootstrap interface command) to lets say 32768 and
> reject any attempt to touch an object with a lower oid.
What do you mean by "touch"? The system catalogs certainly can't
be made read-only in general.
AFAIK we already have sufficient defenses against unwanted hackery on
the system catalogs, and so I don't really see a need for another level
of checking.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2000-11-09 15:53:37 | Re: AW: Unhappy thoughts about pg_dump and objects inherited from template1 |
| Previous Message | Zeugswetter Andreas SB | 2000-11-09 15:47:16 | AW: AW: Unhappy thoughts about pg_dump and objects inhe rited from template1 |