I just noticed that pg_restore executing in "verbose" mode displays the
name of the object being restored, but not its schema.
I'd like to be able to see the fully-qualified object name because
if pg_restore spits out a warning like this:
$ pg_restore -d somedb /path/to/dumpfile.pgd
pg_resto
Kodamasimham Pridhvi (MT2012066)
wrote:
> We students of International Institute of Information Technology
> Bangalore India, are interested to contribute to PostgreSQL
> development. We identified some modules from ToDo list to which
> we want to contribute.We want to begin with an simple modul
Greg Stark writes:
> Writing out each guc in a separate file is a singularly bad idea. It's
I'm not buying into any of your arguments here, and have something to
add to that part:
> I'm not even clear we do want this in /etc since none of our GUC
> options are repeatable things like Apache virtu
On Sat, Aug 3, 2013 at 5:43 AM, Alvaro Herrera wrote:
> Tomas Vondra wrote:
>
> > I'm learning how to use the "background worker processes" commited in
> > 9.3. The usage basics are quite nicely illustrated in the worker_spi
> > extension (kudos to those who designed the feature / extension).
>
>
(2013/08/02 21:19), Robert Haas wrote:
On Fri, Aug 2, 2013 at 8:17 AM, Tom Lane wrote:
Robert Haas writes:
On Fri, Jul 26, 2013 at 8:27 AM, Tom Lane wrote:
would you expect crash recovery to notice the disappearance of a file
that was touched nowhere in the replayed actions?
Eh, maybe no
Hi,
I made a patch for REL9_3_STABLE which gets rid of
old promote processing. please check it.
This patch make PostgreSQL do fast promoting(*) always.
(*) which means skipping long checkpoint before increasing
timeline.
And after this, I'll do make another patch for unlinking files which are
cre
