| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_get_triggerdef in pg_dump |
| Date: | 2003-06-17 03:53:34 |
| Message-ID: | 125c01c33484$070c4d40$6500a8c0@fhp.internal |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Seems like a good idea to me --- we've been trying to reduce pg_dump's
> knowledge of backend nitty-gritty, and this would be another small step
> in the right direction.
>
> > Also, it doesn't format them as nicely as the current pg_dump code...
>
> That's fixable no? I guess you might want to consider what psql's \d
> display will look like too, but I don't recall that we ever promised
> anyone that the pg_get_xxx functions would output no unnecessary
> whitespace.
We make pg_get_xxx2 functions that return a formatted version. Internally,
we just add an extra boolean parameter to the pg_get_triggerdef() function
in ruleutils and we call that true or false depending...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Björklund | 2003-06-17 04:51:50 | Re: confused with encodings |
| Previous Message | Tom Lane | 2003-06-17 03:44:56 | Re: pg_get_triggerdef in pg_dump |