One more question. Does the SET PGPASSWORD sets pass for the role? If
not how to set the password for the role using the script provided.
2010/10/25 Thomas Kellerer :
> Lukasz Brodziak, 25.10.2010 15:49:
>>
>> Hello,
>>
>> What I need to do is create a batch file to be sent to client in which
>> I
> You can check if PITR is disabled by executing:
> SHOW archive_command;
> At a psql prompt. If that's empty, then you turned it off, and it isn't
involved in the shutdown issue you have anymore.
Yes, I could see empty value here.
> Take a look at what processes are still running against the da
Nick writes:
> It seems like the problem is a function of how many databases there are.
Yeah, I can reproduce this in HEAD. Create a hundred or so databases,
and make sure there's a stats table entry for each, eg
create database d0;
\c d0
create table t1 as select generate_series(1,10) x;
c
Nick wrote:
> Kevin Grittner wrote:
>
>> I've not seen anything remotely like that. I wonder what's
>> different
>
> I did a test with the same postgres build (and autovacuum_naptime
> = 1 as well) on the same OS with only the system databases
> (postgres, template0, template1), and after
On Fri, Oct 22, 2010 at 11:17 AM, Kevin Grittner
wrote:
> I've not seen anything remotely like that. I wonder what's
> different
I did a test with the same postgres build (and autovacuum_naptime = 1
as well) on the same OS with only the system databases (postgres,
template0, template1), and
Gnanakumar wrote:
1. What could be the root cause of PostgreSQL server not shutting
down ever?
2. Am I following a different/incorrect way of disabling PITR?
You can check if PITR is disabled by executing:
SHOW archive_command;
At a psql prompt. If that's empty, then you turned it off, an
Lukasz Brodziak, 25.10.2010 15:49:
Hello,
What I need to do is create a batch file to be sent to client in which
I have to perform create role statement. Best thing would be if the
user didn't see what is happening in the console (is there a @echo off
equivalent for psql). Can anyone help me wit
Hello,
What I need to do is create a batch file to be sent to client in which
I have to perform create role statement. Best thing would be if the
user didn't see what is happening in the console (is there a @echo off
equivalent for psql). Can anyone help me with this.
--
Łukasz Brodziak
--
Sen
Hi,
My production server is running PostgreSQL v8.2.3 on CentOS release 5.2
(Final).
I've setup PITR in my production server. For some reason, after setting up
PITR, we're not able to manage and maintain it.
PITR SETUP DETAILS
We've 2 drives. Primary drive (pgsql/data/ directory resides) is 40
