Thank you for your quick reply.
Well I am using windows XP and I have PgAdmin III 1.12.2 installed. I used
backup to take the backup of the database in UTF-8 format. MY pg_dump and
pg_restore both header version are 9.0.3.
The target PC where I want to restore my database also has windows xp
inst
On Wed, Apr 13, 2011 at 8:53 PM, Alanoly Andrews wrote:
> Is it possible to set up a warm standby pair of postgres instances without
> using the pg_standby utility? The PG manuals appear to say it is possible.
> But I don’t see the details of how to set this up. How do you keep the
> standby inst
Hello,
Is it possible to set up a warm standby pair of postgres instances without
using the pg_standby utility? The PG manuals appear to say it is possible. But
I don't see the details of how to set this up. How do you keep the standby
instance in permanent recovery mode?
Thanks.
Alanoly.
**
Simon Riggs writes:
> 2011/4/13 Tom Lane :
>> Short answer is to test the case you have in mind and see.
> That's the long answer, not least because the absence of a failure in
> a test is not conclusive proof that it won't fail at some point in the
> future while in production.
Not really. Eve
2011/4/13 Tom Lane :
> Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= writes:
>> On Wed, 2011-04-13 at 23:23 +0530, raghu ram wrote:
>>> Is there any limitations to configure streaming replication between
>>> different operating systems i.e solaris 64 bit to RHEL 64 bit.
>
>> It won't work.
>
> As long as it'
since your onine logs are in different endian notation. I do not see how
it would work. Sony may be an option in this case.
Andrew Shved
From:
Tom Lane
To:
Devrim GÜNDÜZ
Cc:
raghu ram , pgsql-admin@postgresql.org,
pgsql-gene...@postgresql.org
Date:
04/13/2011 02:14 PM
Subject:
Re: [ADMIN]
just hit me what if we use pg_standby and convert archive logs from one
notation to the other. and after apply them to our standby. can this
work?
Andrew Shved
DBA, Symcor Inc, Delivery Support Services
( Phone: 905-273-1433
( BlackBerry: 416-803-2675
* Email: ash...@symcor.com
From:
Tom La
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= writes:
> On Wed, 2011-04-13 at 23:23 +0530, raghu ram wrote:
>> Is there any limitations to configure streaming replication between
>> different operating systems i.e solaris 64 bit to RHEL 64 bit.
> It won't work.
As long as it's the same machine architectur
On Wed, Apr 13, 2011 at 11:23:24PM +0530, raghu ram wrote:
> Hi,
>
> Is there any limitations to configure streaming replication between
> different operating systems i.e solaris 64 bit to RHEL 64 bit.
I personally wouldn't be willing to use anything except identical
binaries for the back end, an
Hi,
On Wed, 2011-04-13 at 23:23 +0530, raghu ram wrote:
> Is there any limitations to configure streaming replication between
> different operating systems i.e solaris 64 bit to RHEL 64 bit.
It won't work.
Regards,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enter
Hi,
Is there any limitations to configure streaming replication between
different operating systems i.e solaris 64 bit to RHEL 64 bit.
--Raghu Ram
Eric Comeau wrote:
> We currently have statement timeout set
>
> statement_timeout = 1080 # 3 hrs
>
> and we receive the following in the postgresql.log
>
>[1-1] ERROR: canceling statement due to statement timeout
>
> Is there a way to have the SQL statement logged as well?
We currently have statement timeout set
statement_timeout = 1080 # 3 hrs
and we receive the following in the postgresql.log
[1-1] ERROR: canceling statement due to statement timeout
Is there a way to have the SQL statement logged as well?
We have set the log_min_duration_state
Attached Error Message shows, that pgAdmin's pg_restore is not compatible with
the version of pg_dump binary which you have used to take the backup
Please let me know, How did you take the backup? and Please try with same
version of pg_restore, which is of pg_dump.
To find the version of pg_dum
From: "Oliver Jowett"
If the server is shut down mid-query, doesn't the backend complete the
current query cycle before closing the connection?
i.e. we'd see ErrorResponse, ReadyForQuery, and return control to the
app before seeing EOF anyway?
The protocol spec is a bit vague there.
From an o
On 13 April 2011 21:57, Donald Fraser wrote:
> Technically yes. When performing a read on the socket you get -1 indicating
> EOF or remote socket closed. You don't get an IO error.
> The difficult part is what was the client doing when the server closes the
> socket?
> If the client wasn't doing
From: "Kevin Grittner"
"Donald Fraser" wrote:
the JDBC driver does know that the server has terminated the
connection [...] (via end of stream or EOF).
Is the error class "57" a better prefix for this type of error?
Possibly. Is it really true that the client will see a clean close
for
17 matches
Mail list logo
