| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | martin(at)biochemistry(dot)ucl(dot)ac(dot)uk |
| Cc: | scrappy(at)hub(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] How to...? |
| Date: | 1998-03-09 15:14:51 |
| Message-ID: | 199803091514.KAA01864@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I do think it would be a good idea if the pg_dumpall from the new release
> looked for these now-reserved column names and warned the user. You could
> then at least know where problems will occur. In upgrades from d/b versions
> which support ALTER TABLE xxx RENAME COLUMN yyy TO zzz, you would actually
> be able to do something about it before re-dumping...
pg_dumpall is just a shell script. You would have to do it in pg_dump.
I hesistate to meddle with that code unless I have good reason for it.
We could have a separate function that scans pg_attribute looking for
bad column names.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maurice Gittens | 1998-03-09 15:36:07 | Re: [HACKERS] newoid in invapi.c |
| Previous Message | Jan Wieck | 1998-03-09 15:08:55 | Re: [HACKERS] create trigger question |