On Wed, Sep 26, 2012 at 5:21 AM, Albe Laurenz wrote:
> But according to what you wrote before you start the server
> with -D /staging/9.1/main.
> That means that /staging/9.1/main/pg_xlog contains the active
> WAL files, right?
>
> So the restore_command 'cp /staging/9.1/main/pg_xlog/%f "%p"'
> wo
> /staging/9.1/main/pg_xlog is really archive directory? restore_command
> should be set to the command which copies the archived WAL files from
> the archive area.
Yes. This is the archive directory.
This begs another question, does a replicant write its own wal files to disk?
--
Sent via pgs
Hi folks, we're snapshotting at san level, two volumes containing a
postgres 9.1.5 database, and pg_xlog respectively.
This database cluster is a streaming replicant.
We're stopping the database completely, taking the snapshots,
restarting the database.
I export these snapshots as luns to a VM, mou
On Fri, Mar 9, 2012 at 2:02 PM, Filippos wrote:
> Manager for PostgreSQL seems to be covering most of my 'requirements'. in
> general the most important requirement we have is to be able to handle the
> active sessions of the server. This means, to have an overview of what is
> actually running, k
On Wed, Feb 22, 2012 at 7:08 PM, Philip Edelbrock
wrote:
> The question is, is there a way to keep availability of the app 100% yet keep
> the database maintained without the drive filling up? Or is it just the
> nature of the beast that a full vacuum needs to be done periodically?
Short answe
Hi folks,
current configuration has queries that take more than 30 seconds getting logged.
The actual query itself is full of $1 $2 $3 etc, any idea why those
vars arent logged with their values expanded?
Thanks
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to
On Wed, Jan 18, 2012 at 2:17 PM, Scott Ribe wrote:
> On Jan 18, 2012, at 11:59 AM, Tom Lane wrote:
>
>> AFAIR there is no specified order. It probably just seqscans pg_class,
>> so whatever physical order those tuples happen to have today is it.
>
> I'm pretty sure he meant: "in the case when CLU
On Wed, Jan 18, 2012 at 10:08 AM, Kevin Grittner
wrote:
>> Also, I've been tasked with finding and listing all the tables
>> that get CLUSTER'd when CLUSTER with no args is executed,
>
> http://www.postgresql.org/docs/8.1/interactive/catalog-pg-index.html
select relname as table from pg_class joi
Hi folks...pgsql 8.1 (we're migrating to 9.1 later this year).
Two things:
When running CLUSTER with no args, on tables with multiple indexes, do
I understand correctly that the tables' primary key is the default
index used?
Also, I've been tasked with finding and listing all the tables that
get
