Skip site navigation (1) Skip section navigation (2)

Re: Shared pg_xlog directory/partition and warm standby

From: Devrim GUNDUZ <devrim(at)CommandPrompt(dot)com>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Shared pg_xlog directory/partition and warm standby
Date: 2006-11-27 22:31:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

On Mon, 2006-11-27 at 12:14 -0600, Jim C. Nasby wrote:
> The only difference I can think of is not having to copy logfiles
> around, but presumably that could be addressed by using hardlinks
> instead of actually copying (at least on unix...) Maybe Devrim
> has something else in mind? 

What I was thinking is to find a way to reduce network traffic in
high-volume environments. If the archive_timeout is set to a really low
value, such as 1 or 2 seconds, it may result in a high traffic.

I thought that if both servers are in the same network, or better,
directly connected to each other, they could share the same partition so
that no network activity occurs.

Anyway, I haven't tried this feature yet on my test server, etc. I am
just trying to understand what's going on and what can be done with this

The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG -

In response to


pgsql-hackers by date

Next:From: Neil ConwayDate: 2006-11-27 22:45:00
Subject: Re: Storing a dynahash for an entire connection or
Previous:From: Peter NixonnDate: 2006-11-27 22:17:20
Subject: Re: Incrementing INET fields

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group