OK, I have added a new pg_dump TODO section with adjustments based on
feedback from original list:
* pg_dump
o Allow pg_dumpall to use non-text output formats
o Have pg_dump use multi-statement transactions for INSERT dumps
o -Allow pg_dump to dump CREATE CONVERSION (Chris
Being able to export to other dbs will get us _more_ users, not less.
Without some type of corresponding import utility that seems logically false.
Nope. Consider it like this. How many companies are going to move to
PostgreSQL from Oracle if they cannot dump their data back to Oracle as
a fai
On Friday 13 August 2004 00:13, Christopher Kings-Lynne wrote:
> > That should make exporting to other DBs a lot easier. Of course, that
> > could be cutting our own throat too ...
>
> It won't make any difference to anything. You can already dump in
> INSERT format.
>
> Being able to export to ot
Tom Lane wrote:
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
That should make exporting to other DBs a lot easier. Of course, that
could be cutting our own throat too ...
It won't make any difference to anything. You can already dump in
INSERT format.
And anyway, the DD
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> That should make exporting to other DBs a lot easier. Of course, that
>> could be cutting our own throat too ...
> It won't make any difference to anything. You can already dump in
> INSERT format.
And anyway, the DDL peculiarities would b
That should make exporting to other DBs a lot easier. Of course, that
could be cutting our own throat too ...
It won't make any difference to anything. You can already dump in
INSERT format.
Being able to export to other dbs will get us _more_ users, not less.
Chris
---(
Christopher Kings-Lynne wrote:
OK, everything for pg_dump TODO I can think of:
[snip]
* Export to other database (eg. Oracle, MySQL and DB2) formats
This strikes me as a can of worms, or to mix metaphors a bit, a rathole
from which we might never emerge.
I did have a thought the other day - now
Yep, a whole section for pg_dump features and bugs would be nice.
Bruce Momjian wrote:
Do you want any of these added to the TODO?
---
Christopher Kings-Lynne wrote:
And I forgot to add:
* Allow dumping/restoring of any number
Do you want any of these added to the TODO?
---
Christopher Kings-Lynne wrote:
> And I forgot to add:
>
> * Allow dumping/restoring of any number of specific objects and types
>
> Chris
>
> Christopher Kings-Lynne wrote:
And I forgot to add:
* Allow dumping/restoring of any number of specific objects and types
Chris
Christopher Kings-Lynne wrote:
OK, everything for pg_dump TODO I can think of:
pg_dump/pg_dumpall/pg_restore
* Add dumping of comments on composite type columns
* Add dumping of comments on index column
OK, everything for pg_dump TODO I can think of:
pg_dump/pg_dumpall/pg_restore
* Add dumping of comments on composite type columns
* Add dumping of comments on index columns
* Replace crude DELETE FROM way of dumping cleaning of users and groups
with separate DROP commands
* Add dumping and restori
Yes, shoot over that the section should contain.
---
Christopher Kings-Lynne wrote:
> Perhaps. I was also thinking that maybe it's time to combine pg_dumpall
> and pg_dump into a single utility. At the moment, I can't see
Perhaps. I was also thinking that maybe it's time to combine pg_dumpall
and pg_dump into a single utility. At the moment, I can't see how
pg_dumpall can ever have a -Fc option, since it will be messy to
interact with the pg_dump processes.
I was thinking a pg_export utility that can output to
I just got an autoreply from David stating he will be away until August
9 if we want this functionality we have to code it ourselves. If not it
can wait until the next major release.
It can wait --- it was submitted after feature freeze anyway, and we
certainly have more than enough other things t
TODO item?
---
Christopher Kings-Lynne wrote:
> >>I just got an autoreply from David stating he will be away until August
> >>9 if we want this functionality we have to code it ourselves. If not it
> >>can wait until the ne
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I just got an autoreply from David stating he will be away until August
> 9 if we want this functionality we have to code it ourselves. If not it
> can wait until the next major release.
It can wait --- it was submitted after feature freeze anyway, and
I just got an autoreply from David stating he will be away until August
9 if we want this functionality we have to code it ourselves. If not it
can wait until the next major release.
If anyone wants the original patch I can supply it.
Is anyone working on this patch?
---
Tom Lane wrote:
> "David F. Skoll" <[EMAIL PROTECTED]> writes:
> > On Wed, 21 Jul 2004, Tom Lane wrote:
> >> pg_dump -t s1.t1 -t s2.t2 -- Dump s1.t1 and s2.t2
>
> > That's a
18 matches
Mail list logo
