> Hi,
>
> Thank you for your soon reply.
>
> I'm trying to set the network timeout related parameters to terminate it.
>
> # i've tried to set postgresql.conf's tcp_keepalives_* but not success.
>
> Regards,
>
> 2013/04/10 14:05、Amit Kapila のメッセージ:
>
>> On Wednesday, April 10, 2013 9:35 AM
> Sent: Wednesday, April 10, 2013 1:49 PM Dang Minh Huong wrote:
> To: Amit Kapila
> Subject: Re: [BUGS] replication_timeout not effective
On Wednesday, April 10, 2013 1:49 PM
> Hi,
>
> Thank you for your soon reply.
>
> I'm trying to set the network timeout related parameters to terminate
> it.
>
Hi Amit,
Thank you for your consideration.
My project not allows to use 9.2 or 9.3.
In 9.3, it sounds replication_timeout is replaced by wal_sender_timeout.
So if it is solved in 9.3 i think there is a way to terminate it.
I hope it is fixed in 9.1 soon
Regards,
2013/04/10 18:33、Amit Kapila
2013/4/9 :
> The following bug has been logged on the website:
>
> Bug reference: 8056
> Logged by: Eugene
> Email address: knowze...@yahoo.com
> PostgreSQL version: 9.2.1
Please update your Postgres to 9.2.4.
> I have hstore installed on my server and it works fine. But somet
Hello,
On Wed, Apr 10, 2013 at 6:57 PM, Dang Minh Huong wrote:
> In 9.3, it sounds replication_timeout is replaced by wal_sender_timeout.
> So if it is solved in 9.3 i think there is a way to terminate it.
> I hope it is fixed in 9.1 soon
Hmm. He said that,
> But in my environment the sender pr
On 2013-04-10 22:38:07 +0900, Kyotaro HORIGUCHI wrote:
> Hello,
>
> On Wed, Apr 10, 2013 at 6:57 PM, Dang Minh Huong wrote:
> > In 9.3, it sounds replication_timeout is replaced by wal_sender_timeout.
> > So if it is solved in 9.3 i think there is a way to terminate it.
> > I hope it is fixed in
Thanks all,
(2013/04/10 22:55), Andres Freund wrote:
On 2013-04-10 22:38:07 +0900, Kyotaro HORIGUCHI wrote:
Hello,
On Wed, Apr 10, 2013 at 6:57 PM, Dang Minh Huong wrote:
In 9.3, it sounds replication_timeout is replaced by wal_sender_timeout.
So if it is solved in 9.3 i think there is a way
On 2013-04-10 23:37:44 +0900, Dang Minh Huong wrote:
> Thanks all,
>
> (2013/04/10 22:55), Andres Freund wrote:
> >On 2013-04-10 22:38:07 +0900, Kyotaro HORIGUCHI wrote:
> >>Hello,
> >>
> >>On Wed, Apr 10, 2013 at 6:57 PM, Dang Minh Huong
> >>wrote:
> >>>In 9.3, it sounds replication_timeout is
2013/04/10 23:44、Andres Freund のメッセージ:
> On 2013-04-10 23:37:44 +0900, Dang Minh Huong wrote:
>> Thanks all,
>>
>> (2013/04/10 22:55), Andres Freund wrote:
>>> On 2013-04-10 22:38:07 +0900, Kyotaro HORIGUCHI wrote:
Hello,
On Wed, Apr 10, 2013 at 6:57 PM, Dang Minh Huong
wr
You mean by running current_schemas(true) on that session?
So far I have remade the hstore functions into this and it seems to be working
for now: (But this happens randomly after time so it might take a day or 2 to
be sure this addresses the issue)
CREATE OR REPLACE FUNCTION accounts.myhstore
On 4/10/2013 11:01 AM, E E wrote:
CREATE OR REPLACE FUNCTION accounts.myhstore_merge(myh hstore, mytext
text[])
RETURNS hstore AS
$BODY$BEGIN
SET search_path TO public;
RETURN myh || hstore(mytext);
END;$BODY$
LANGUAGE plpgsql VOLATILE
COST 100;
public.hstore(...)would have been
11 matches
Mail list logo
