After thinking some more, an expansion on the third possibility:
* Call pg_start_backup on the master. Checkpoint the
non-participating replica. Copy data dirs from non-participating
replica. Copy xlogs from master. Call pg_stop_backup on the master.
Copy final xlogs from master. This would move
On 06/26/12 9:04 PM, Cody Cutrer wrote:
* Instead of using pg_basebackup, manually call pg_start_backup and
pg_stop_backup against the new master, and rsync the data over, since
presumably little has changed since a timeline divergence
I believe thats the correct method.
--
john r pierce
I've got a few questions about initing a new replica. We have a
modestly large DB cluster with a master and two replicas running with
streaming replication. We tend to switch which one is the master
fairly often, shuffling hardware, upgrading kernels, etc. However,
every time we fail over, we have
Hi all,
The tip beneath \df on psql's documentation page[0] advises the user:
| Tip: To look up functions taking arguments or returning values
| of a specific type, use your pager's search capability to scroll
| through the \df output.
(This tip was put in[1] as an alternative to having a real '
On 06/26/2012 05:18 AM, Stuart Bishop wrote:
On Tue, Jun 26, 2012 at 6:47 AM, Steve Crawford
wrote:
...
I'm seeing troubling messages in the log. While running pgbench I
see the following types of messages on the master every minute or few:
2012-06-25 11:36:26 PDT FATAL: could not send data
On Wed, Jun 20, 2012 at 9:52 PM, utsav wrote:
> merlin can u please suggest any solution for achiving this . I have tried
> array but still i am not getting how to return different array and for
> returning array i must have to pass one array in input parameter and that
> only i can return that is
anyone had faced the same issue than pl help..
merlin : i am waiting for your reply ...
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/RETURNING-MORE-THAN-ONE-CUSTOM-TYPE-FROM-FUNCTION-tp5712546p5714315.html
Sent from the PostgreSQL - general mailing list archive at N
On Tue, Jun 26, 2012 at 09:13:44AM -0700, Steve Crawford wrote:
- On 06/26/2012 08:16 AM, David Kerr wrote:
- >On 06/26/2012 05:11 AM, Stuart Bishop wrote:
- >>On Tue, Jun 26, 2012 at 6:21 AM, David Kerr wrote:
- >>>On Mon, Jun 25, 2012 at 02:17:22PM -0700, Steve Crawford wrote:
- >>>- On 06/25/20
On 06/26/2012 08:16 AM, David Kerr wrote:
On 06/26/2012 05:11 AM, Stuart Bishop wrote:
On Tue, Jun 26, 2012 at 6:21 AM, David Kerr wrote:
On Mon, Jun 25, 2012 at 02:17:22PM -0700, Steve Crawford wrote:
- On 06/25/2012 01:17 PM, David Kerr wrote:
->Howdy,
->
->When calculating Replication lag,
On 06/26/2012 05:11 AM, Stuart Bishop wrote:
On Tue, Jun 26, 2012 at 6:21 AM, David Kerr wrote:
On Mon, Jun 25, 2012 at 02:17:22PM -0700, Steve Crawford wrote:
- On 06/25/2012 01:17 PM, David Kerr wrote:
->Howdy,
->
->When calculating Replication lag, I know that we have to compare the
->pg_cur
On 06/26/2012 05:11 AM, Stuart Bishop wrote:
On Tue, Jun 26, 2012 at 6:21 AM, David Kerr wrote:
On Mon, Jun 25, 2012 at 02:17:22PM -0700, Steve Crawford wrote:
- On 06/25/2012 01:17 PM, David Kerr wrote:
->Howdy,
->
->When calculating Replication lag, I know that we have to compare the
->pg_cur
Christoph Zwerschke wrote:
> Our developers like the dblink modules, so I have installed it into
the
> template1 database. They also like to import old database dumps after
> creating new databases with dbcreate. But then they get irritated by
the
> error messages saying that the dblink functions a
Jasen Betts writes:
> On 2012-06-26, Vlad Arkhipov wrote:
>> Is it guaranteed that if txid2 > txid1 then current_timestamp in
>> transaction 2 >= current_timestamp in transaction 1?
> no.
To enlarge on that: current_timestamp is set at the moment of receipt
from the client of a transaction's
On Tue, Jun 26, 2012 at 6:47 AM, Steve Crawford
wrote:
> The documentation says "To use streaming replication, set up a file-based
> log-shipping standby server as described in Section 25.2" however I'm
> not using any of the archive or restore commands but instead use
> pg_basebackup to do t
On Tue, Jun 26, 2012 at 6:21 AM, David Kerr wrote:
> On Mon, Jun 25, 2012 at 02:17:22PM -0700, Steve Crawford wrote:
> - On 06/25/2012 01:17 PM, David Kerr wrote:
> - >Howdy,
> - >
> - >When calculating Replication lag, I know that we have to compare the
> - >pg_current_xlog_location
> - >to pg_la
On 2012-06-26, Vlad Arkhipov wrote:
> Is it guaranteed that if txid2 > txid1 then current_timestamp in
> transaction 2 >= current_timestamp in transaction 1?
no.
--
⚂⚃ 100% natural
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
On 26 June 2012 10:59, Christoph Zwerschke wrote:
> Our developers like the dblink modules, so I have installed it into the
> template1 database. They also like to import old database dumps after
> creating new databases with dbcreate. But then they get irritated by the
> error messages saying tha
Our developers like the dblink modules, so I have installed it into the
template1 database. They also like to import old database dumps after
creating new databases with dbcreate. But then they get irritated by the
error messages saying that the dblink functions already exist, because
these fun
18 matches
Mail list logo
