Re: 9.3 Beta1 status report - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: 9.3 Beta1 status report
Date
Msg-id 20130506145737.GD26481@momjian.us
Whole thread Raw
In response to Re: 9.3 Beta1 status report  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Sun, May  5, 2013 at 06:59:28PM -0400, Andrew Dunstan wrote:
> >    > I think this is equally important for restoration of dumps, if
> >    the restoration
> >    > is run all in one transaction.  (Making the dump and restoring
> >    it have similar
> >    > locking and unlocking patterns)
> >
> >    Do you have proposed wording?  I can't say just dump/restore as it
> >    only
> >    helps with _logical_ dump and _logical_ restore, and we don't have a
> >    clear word for logical restore, as it could be pg_restore or piped
> >    into
> >    psql.  We could do:
> >
> >            that hold many locks; it is particularly useful for
> >    pg_dump and restore.
> >
> >    but "restore" seems very vague.
> >
> >
> >
> >Yeah, I wasn't sure about how to work that either.
> >
> >"...and the restore of such dumps."?
> >
> 
> s/restore/restoration/

I like that even better!  Done.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: 9.3 Beta1 status report
Next
From: Dimitri Fontaine
Date:
Subject: Re: erroneous restore into pg_catalog schema