| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Phil Frost <indigo(at)bitglue(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: feature request: pg_dump --view |
| Date: | 2006-07-19 13:44:33 |
| Message-ID: | 20060719134433.GD20016@kenobi.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Andrew Dunstan (andrew(at)dunslane(dot)net) wrote:
> elein wrote:
> >>pg_dump -t <view_name> will work.
> >
> >Oh, you got me all worked up. I was reading this as a way to
> >dump the CONTENTS of a view not the DEFINITION of a view.
> >I thought someone sneaked in pg_dump of a query in there.
> >
> >
>
> How would you load such a dump, since views are by default select-only?
Create the appropriate table definition, and then load it up? Of
course, an option to have the pg_dump include the table definition
derived from the view would be nice also.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phil Frost | 2006-07-19 14:05:32 | Re: lastval exposes information that currval does not |
| Previous Message | Dave Page | 2006-07-19 13:19:02 | Re: password is no required, authentication is overridden |