On 8/2/13 4:48 PM, Stephen Frost wrote:
* Josh Berkus (j...@agliodbs.com) wrote:
I really think this is the wrong approach. If we start removing
unsafe parameters from ALTER SYSTEM SET, we basically hobble the
feature to the point of uselessness. Out of the 15 or so parameters 80%
of our
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
(2013/08/02 21:19), Robert Haas wrote:
On Fri, Aug 2, 2013 at 8:17 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 26, 2013 at 8:27 AM, Tom Lane t...@sss.pgh.pa.us wrote:
would you expect crash recovery to notice the disappearance of a file
that
On Sat, Aug 3, 2013 at 5:43 AM, Alvaro Herrera alvhe...@2ndquadrant.comwrote:
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 /
Greg Stark st...@mit.edu 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
Kodamasimham Pridhvi (MT2012066) pridhvi.kodamasim...@iiitb.org
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
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
