From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 9.3 Beta1 status report |
Date: | 2013-05-06 14:57:37 |
Message-ID: | 20130506145737.GD26481@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2013-05-06 14:58:17 | Re: erroneous restore into pg_catalog schema |
Previous Message | Bruce Momjian | 2013-05-06 14:56:44 | Re: 9.3 Beta1 status report |