dumping - Search results , p.2
Mailing lists >> pgsql-patches >> Thread
2008-07-26 13:56:38 | Re: pg_dump additional options for performance (Simon Riggs)
dump tables separately for performance reasons. There are documented tests showing 100% gains using this
Mailing lists >> pgsql-patches >> Thread
2008-07-26 13:54:17 | Re: pg_dump additional options for performance (Stephen Frost)
dump files sometimes, and there's no way I'm going to dump that into
Mailing lists >> pgsql-patches >> Thread
2008-07-26 13:33:45 | Re: pg_dump additional options for performance (Tom Lane)
Stephen Frost
Mailing lists >> pgsql-patches >> Thread
2008-07-26 13:20:26 | Re: pg_dump additional options for performance (Tom Lane)
dump -Fc >whole.dump pg_restore --schema-before-data whole.dump >before.sql pg_restore
Mailing lists >> pgsql-patches >> Thread
2008-07-26 12:11:33 | Re: pg_dump additional options for performance (Stephen Frost)
dumped at the time of that object getting dumped. Comments make sense as an extention
Mailing lists >> pgsql-patches >> Thread
2008-07-26 05:58:53 | Re: pg_dump additional options for performance (Simon Riggs)
dump into multiple pieces. The equivalent capability on restore is *not* required, because once the dump
Mailing lists >> pgsql-patches >> Thread
2008-07-25 23:39:42 | Re: pg_dump additional options for performance (Greg Sabino Mullane)
dumps as well then? I'm not comfortable with corner cases for pg_restore backwards
Mailing lists >> pgsql-patches >> Thread
2008-07-25 20:16:52 | Re: pg_dump additional options for performance (Tom Lane)
dump. If none are specified (which would in itself be a useless combination) then the default
Mailing lists >> pgsql-patches >> Thread
2008-07-24 05:50:36 | Re: pg_dump additional options for performance (Simon Riggs)
On Thu, 2008-07-24 at 03:54 -0400, Tom Lane wrote: Removed, thanks. Unrelated
Mailing lists >> pgsql-patches >> Thread
2008-07-24 04:54:25 | Re: pg_dump additional options for performance (Tom Lane)
Simon Riggs
Mailing lists >> pgsql-patches >> Thread
2008-07-24 04:31:07 | Re: pg_dump additional options for performance (Simon Riggs)
dump, since this would currently dump enums if --data-only was specified, which in my understanding
Mailing lists >> pgsql-patches >> Thread
2008-07-24 00:24:59 | Re: pg_dump additional options for performance (Stephen Frost)
dumped */ ! if (!tbinfo->dobj.dump) continue; if (g_verbose) --- 3459,3465 ---- continue; /* Ignore indexes of tables
Mailing lists >> pgsql-patches >> Thread
2008-07-23 14:27:14 | Re: pg_dump additional options for performance (Simon Riggs)
On Wed, 2008-07-23 at 17:40 +0100, Simon Riggs wrote: ...and with command
Mailing lists >> pgsql-patches >> Thread
2008-07-23 14:03:00 | Re: pg_dump additional options for performance (Simon Riggs)
On Mon, 2008-07-21 at 07:56 -0400, Stephen Frost wrote: OK, Mr.Reviewer
Mailing lists >> pgsql-patches >> Thread
2008-07-22 03:29:21 | Re: pg_dump additional options for performance (Simon Riggs)
dump. But that seems an unreliable prop, so I am inclined towards the inclusive approach