any other clue about this problem ?? Have anybody seen the same problem ??
Greg Stark-5 wrote:
>
> On Fri, Dec 18, 2009 at 6:59 PM, tamanna madaan
> wrote:
>> I am using postgres-8.1.2 and slony-1.1.5 for replication.
>>
>
> I don't know about your Slony
why not it simply come out giving
some error
instead of getting stuck for an indefinite period.
Thanks...
Tamanna
this query, also
resolved the issue. That means after restart, the process was able to
update the same table. Had it been waiting for a lock before , it wouldn't
have been able to update the table after restart either.
Regards
Tamanna
-Original Message-
From: Tom Lane [mai
There doesn't seem to be any locking issue .
Can anyone please shed some light on this issue .
Thanks...
Tamanna
From: Alban Hertroys [mailto:dal...@solfertje.student.utwente.nl]
Sent: Fri 12/31/2010 3:28 PM
To: tamanna madaan
Cc: Tom Lane; pgsql-general@post
king issue either .
Can anyone please shed some light on this issue .
Thanks...
Tamanna
application is
multi threaded .
Tamanna
From: Merlin Moncure [mailto:mmonc...@gmail.com]
Sent: Fri 3/18/2011 8:56 PM
To: tamanna madaan
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] SOCK_wait_for_ready function call caused a query to get
stuck
On Fri, Mar
, sl_seqlog etc) are configured
not to be processed by autovacuum . Please let me know what could be the reason
of increasing dead tuples in these tables and postgres getting slow.
Thanks..
Tamanna
e getting connection to
postgres while executing the above query ,
I want the query to exit . How can I set connection timeout for that ??
Thanks..
Tamanna
Thanks Daniele
-Original Message-
From: Daniele Varrazzo [mailto:daniele.varra...@gmail.com]
Sent: Wed 4/20/2011 1:15 AM
To: tamanna madaan
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] setting connection/ query timeout
On Tue, Apr 19, 2011 at 8:09 PM, tamanna madaan
wrote
too frequently (19 seconds apart)"
I am not sure when these all errors started coming . Just noticed these
when database size grew huge and it became slow.
Can anybody shed some light on it if these errors are related or what could
be the reason for these errors .
Thanks..
Tamanna
on that.
Thanks in Advance .
Tamanna
terval and
tcp_keepalives_count configurations in postgresql.conf to get rid of this
"idle in transaction" process after a certain amount of time . Will this
help or not ??
Thanks...
Tamanna
On Tue, Aug 16, 2011 at 11:56 AM, Abbas wrote:
>
> Best Regards,
> Abbas
>
>
Can anyone please suggest me on this .
Thanks..
Tamanna
On Thu, Aug 18, 2011 at 2:47 PM, tamanna madaan <
tamanna.mad...@globallogic.com> wrote:
> Hi
>
> Yes , restarting the slon resolves the issue. But. there are other
> processes also in my application which connect t
statement in "test" or it will continue with the
next statement parallely while "test1" is being executed.
3. Moreover, will test1 be called sequentially in order for all the three
arguments i.e arg1 first and arg3 in last. Or there can be a different
order.
Thanks..
Ta
s error in some way ( just a guess) . If not, then what can be the
reason of this error ??
Please help.
Thanks..
Tamanna
this , the problem had occurred on 8.4.1 and a patch
(snapmgr-bugfix-rehash-2.patch ) was provided on 8.4.1 to circumvent this
problem.
This patch worked fine . I was just wondering if this patch
is backward compatible and can it be merged with 8.1.2
to get it working. Any suggestions ??
Thanks
Ta
8.4.2 was released i.e 14th Dec.,2009.
Its not there in any of the 8.1 releases after that i.e 8.1.20 and 21.
So , it seems that this fix is not included in 8.1. Do you have any
idea what could be the reason.
Thanks..
Tamanna
-Original Message-
From: Scott Marlowe [mailto:scott
a user
defined function ??
How can I get function name corresponding 19119
Thanks..
Tamanna
Please help
Thanks..
Tamanna
-Original Message-
From: David Fetter [mailto:da...@fetter.org]
Sent: Saturday, July 17, 2010 8:45 PM
To: Merlin Moncure
Cc: tamanna madaan; pgsql-general@postgresql.org
Subject: Re: [GENERAL] cache lookup failed for function 19119
On Thu, Jul 15,
Hi All
Any idea about this problem ??
Thanks..
Tamanna
-Original Message-
From: tamanna madaan
Sent: Fri 8/20/2010 11:54 AM
To: pgsql-general@postgresql.org
Subject: error while autovacuuming
Hi All
I am using a cluster setup with two nodes in it . postgres version is 8.1.2 and
Hi All
Can a postgres patch for the fix ( provided in postgres-8.1.6 for
autovacuum error ) be included with the postgres version I am using i.e
postgres 8.1.2 so that I don't have to upgrade to 8.1.21 ??
Please reply
Thanks...
Tamanna
-Original Message-
From: tamanna madaan
I'll
have to upgrade slony as well.
Is there any compatibility matrix between slony and postgres . where can
I find that ??
Please Reply ...
Thanks...
Tamanna
-Original Message-
From: Michael Glaesemann [mailto:g...@seespotcode.net]
Sent: Thursday, September 09, 2010 1:49
Hi All
Can I upgrade directly to postgres-8.4 . I think it would also be having
the fix for "autovacuum error" which is there in postgres-8.1.6 . But
please confirm .
Thanks..
Tamanna
-Original Message-----
From: tamanna madaan
Sent: Thursday, September 09, 2010 2:40 AM
To
ere I can find the information about this fix and code changes done
for this fix.
Thanks..
Tamanna
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: Thursday, September 09, 2010 1:45 AM
To: tamanna madaan
Cc: pgsql-general@postgresql.org
Subject: Re: [GE
if there is any postgres patch with
the fix for autovacuum error
, where can I find that patch and can this patch be applied on
postgres-8.1.2 .
Please reply ...
Thanks...
Tamanna
Hi David
You mean to say , change the binary to postgres-8.1.21 and then restart
postgres . that's it ?? please confirm..
Thanks..
Tamanna
-Original Message-
From: David Fetter [mailto:da...@fetter.org]
Sent: Friday, September 10, 2010 2:06 AM
To: tamanna madaan
Cc: Scott Ma
Ok . Thanks ..
-Original Message-
From: David Fetter [mailto:da...@fetter.org]
Sent: Friday, September 10, 2010 2:36 AM
To: tamanna madaan
Cc: Scott Marlowe; pgsql-general@postgresql.org
Subject: Re: [GENERAL] error while autovacuuming
On Fri, Sep 10, 2010 at 02:35:29AM +0530, tamanna
ound steps, then autovacuum will start vacuuming all
the 4 databases
every 20 mins as I mentioned above. So, please confirm if in this case
I need to do 'vacuum freeze' for all the databases or I can skip this
step in workaround procedure.
Thanks..
Tamanna
databases every 20 mins as
I mentioned above.
Please confirm ...
-Original Message-
From: David Fetter [mailto:da...@fetter.org]
Sent: Wednesday, September 15, 2010 3:27 AM
To: tamanna madaan
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] workaround steps for autovaccum probl
Thanks Scott for your reply ...
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: Wednesday, September 15, 2010 7:36 AM
To: tamanna madaan
Cc: David Fetter; pgsql-general@postgresql.org
Subject: Re: [GENERAL] workaround steps for autovaccum problem
On Tue
..
Thanks...
Tamanna
-Original Message-----
From: tamanna madaan
Sent: Thursday, September 09, 2010 7:25 PM
To: 'Michael Glaesemann'; 'Scott Marlowe'
Cc: 'pgsql-general@postgresql.org'
Subject: RE: [GENERAL] error while autovacuuming
Hi All
Can I upgrade dir
Thanks a lot Scott ...
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: Saturday, October 02, 2010 3:14 AM
To: tamanna madaan
Cc: Michael Glaesemann; pgsql-general@postgresql.org
Subject: Re: [GENERAL] error while autovacuuming
On Fri, Oct 1, 2010 at 2:06
red in the table or there are no duplicate
rows but
duplicates are returned while querying the table.
I am using postgres 8.1.2 and slony 1.1.5 .
Please suggest which version of postgres has fix for above mentioned
problem.
Thanks...
Tamanna
s are properly shown as master and slave.
This problem is resolved by dropping the schema used by slony on both the
systems an
then recreating the schema.
I want to know what could be the root cause of logtriggers/denyaccess
triggers getting removed from the tables.
Thanks in advance
Regards
Tamanna
Hi All
I am using postgres-8.1.2.
Can anyone please let me know if autovacuum in postgres-8.1.2 uses
prepared transactions.
Thanks a lot in advance
Regards
Tamanna
Thanks Tom ...
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Tuesday, January 12, 2010 1:35 AM
To: tamanna madaan
Cc: pgsql-general@postgresql.org; Gaurav Katiyar
Subject: Re: [GENERAL] does autovacuum in postgres-8.1.2 use prepared
transactions ??
"tamanna m
upposed to execute) is rebooted . What
could be the reason ??
Thanks...
--
Tamanna Madaan | Associate Consultant | GlobalLogic Inc.
Leaders in Software R&D Services
ARGENTINA | CHILE | CHINA | GERMANY | INDIA | ISRAEL | UKRAINE | UK | USA
Office: +0-120-406-2000 x 2971
www.globallogic.com
twork issues have any role in that . Please help.
Thanks
Regards
Tamanna
On Tue, Nov 29, 2011 at 7:58 AM, Craig Ringer wrote:
> On 11/28/2011 05:30 PM, tamanna madaan wrote:
>
>> Hi All
>> I have postgres installed in cluster setup. My system has a script
>> whic
well, one question : Is tcp-keep-alive enabled by default in postgres-8.1.2 .
I am using postgres on linux platform .
On Tue, Nov 29, 2011 at 8:51 AM, tamanna madaan <
tamanna.mad...@globallogic.com> wrote:
> Hi Craig
>
> Thanks for your reply . But unfortunately I dont ha
using the setsockopt interface. I wonder if
postgres8.1.2 supports / request for system level keepalive control ?? If
not, then which release/version of postgres supports that ??
Thanks...
Tamanna
On Tue, Nov 29, 2011 at 4:56 PM, tamanna madaan <
tamanna.mad...@globallogic.com> wrote:
>
EEPINTVL, in seconds;
# 0 selects the system default
#tcp_keepalives_count = 0 # TCP_KEEPCNT;
# 0 selects the system default
system level setiing :
net.ipv4.tcp_keepalive_time = 7200
net.ipv4.tcp_keepalive_probes = 9
net.ipv4.tcp_keepalive_intvl = 75
Regards
Tamanna
On Thu, De
Hi All
Please help me .
Thanks...
Tamanna
On Mon, Dec 5, 2011 at 12:45 PM, tamanna madaan <
tamanna.mad...@globallogic.com> wrote:
> Hi Tomas
>
> I tried it on the system having postgres-8.4.0 . And the behavior is same
> .
>
> Cluster means a group of machines havi
42 matches
Mail list logo