On 06/08/2012 09:01 AM, Lonni J Friedman wrote:
On Thu, Jun 7, 2012 at 5:07 PM, Jerry Sievers wrote:
You might try stopping pg_basebackup in place with SIGSTOP and check
if problem goes away. SIGCONT and you should start having
sluggishness again.
If verified, then any sort of throttling mec
Hi.
I have this problem:
I have PostgreSQL 9.1.3 and the last night crash it.
This was the first error after an autovacuum (the night before last):
<2012-06-06 00:59:07 MDT814 4fceffbb.32e >LOG: autovacuum: found
orphan temp table "(null)"."tmpmuestadistica" in database "dbRX"
<2012-06-0
On Thu, Jun 7, 2012 at 5:07 PM, Jerry Sievers wrote:
> Lonni J Friedman writes:
>
>> On Thu, Jun 7, 2012 at 12:40 PM, Magnus Hagander wrote:
>>
>>> On Thu, Jun 7, 2012 at 8:04 PM, Lonni J Friedman wrote:
On Thu, Jun 7, 2012 at 10:41 AM, Lonni J Friedman
wrote:
> Greetings,
>
Lonni J Friedman writes:
> On Thu, Jun 7, 2012 at 12:40 PM, Magnus Hagander wrote:
>
>> On Thu, Jun 7, 2012 at 8:04 PM, Lonni J Friedman wrote:
>>> On Thu, Jun 7, 2012 at 10:41 AM, Lonni J Friedman
>>> wrote:
Greetings,
I have a 4 server postgresql-9.1.3 cluster (one master doing st
On Thu, Jun 7, 2012 at 12:40 PM, Magnus Hagander wrote:
> On Thu, Jun 7, 2012 at 8:04 PM, Lonni J Friedman wrote:
>> On Thu, Jun 7, 2012 at 10:41 AM, Lonni J Friedman wrote:
>>> Greetings,
>>> I have a 4 server postgresql-9.1.3 cluster (one master doing streaming
>>> replication to 3 hot standby
On Thu, Jun 7, 2012 at 8:04 PM, Lonni J Friedman wrote:
> On Thu, Jun 7, 2012 at 10:41 AM, Lonni J Friedman wrote:
>> Greetings,
>> I have a 4 server postgresql-9.1.3 cluster (one master doing streaming
>> replication to 3 hot standby servers). All of them are running
>> Fedora-16-x86_64.
>>
>>
Thanks a lot Hari,
very resourceful, you have been very helpful.
cheers,
A.A.
On 06/07/2012 12:47 AM, hari.fu...@gmail.com wrote:
Amador Alvarez writes:
Any idea on doing ("COMMENT ON SCHEMA x IS 'y'") as 'y' variable?
You could use PL/pgSQL's "EXECUTE" for that:
DO $$BEGIN
EXECUTE 'COM
Hi.
I have this problem:
I have PostgreSQL 9.1.3 and the last night crash it.
This was the first error after an autovacuum (the night before last):
<2012-06-06 00:59:07 MDT814 4fceffbb.32e
>LOG: autovacuum: found orphan temp table
"(null)"."tmpmuestadistica" in database
"dbRX"
<2012-06
On Thu, Jun 7, 2012 at 10:41 AM, Lonni J Friedman wrote:
> Greetings,
> I have a 4 server postgresql-9.1.3 cluster (one master doing streaming
> replication to 3 hot standby servers). All of them are running
> Fedora-16-x86_64.
>
> http://wiki.postgresql.org/wiki/Lock_Monitoring
err, i included
Greetings,
I have a 4 server postgresql-9.1.3 cluster (one master doing streaming
replication to 3 hot standby servers). All of them are running
Fedora-16-x86_64.
http://wiki.postgresql.org/wiki/Lock_Monitoring
I'm finding that I cannot runpg_basebackup at all, or it slows down all
SQL queries f
Amador Alvarez writes:
> Any idea on doing ("COMMENT ON SCHEMA x IS 'y'") as 'y' variable?
You could use PL/pgSQL's "EXECUTE" for that:
DO $$BEGIN
EXECUTE 'COMMENT ON SCHEMA myschema IS ''Created ' ||
current_timestamp || ;
END$$;
--
Sent via pgsql-admin mailing list (pgsql-a
11 matches
Mail list logo