| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Suggested "easy" TODO: pg_dump --from-list |
| Date: | 2010-11-24 06:15:43 |
| Message-ID: | 6606.1290579343@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Well, very little about pg_dump is very [E], IMNSHO. The question in my
>> mind here is what format the list file will take
> I was thinking same format as pg_restore -l, only without the dumpIDs.
Nope ... those strings are just helpful comments, they aren't really
guaranteed to be unique identifiers. In any case, it seems unlikely
that a user could expect to get the more complicated cases exactly right
other than by consulting "pg_dump | pg_restore -l" output. Which makes
the use-case kind of dubious to me.
I don't say that this wouldn't be a useful feature, but you need a
better spec than this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radosław Smogura | 2010-11-24 07:07:07 | JDBC and Binary protocol error, for some statements |
| Previous Message | Greg Smith | 2010-11-24 06:11:31 | Re: Horizontal Write Scaling |