From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: playing with catalog tables limits? dangers? was: seq bug 2073 and time machine |
Date: | 2008-08-25 16:07:23 |
Message-ID: | 1206.1219680443@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> writes:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>> If you're feeling corageous, you can remove the pg_depend entries
>> for that sequence. Make sure to try it in a transaction and drop
> I'd like to understand better the risks of being courageous?
> I think my life would be easier if I'd know when it is safe to put
> hands in the system tables.
Well, it's safe if (a) you know what you're doing, (b) you don't
make any mistakes, and (c) you don't forget any changes needed to
keep all the catalogs consistent.
You can protect yourself against (b) by using a transaction, but
the other two tend to require hacker-grade knowledge of how the
backend works, so we try to discourage people from doing it.
pg_depend in particular tends to have rather obscure contents,
and what's worse is that messing it up usually doesn't have any
immediately-obvious consequences.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-08-25 16:14:41 | Re: Dump/restore with bad data and large objects |
Previous Message | John T. Dow | 2008-08-25 14:21:54 | Dump/restore with bad data and large objects |