Re: Feature freeze date for 8.1

From: <adnandursun(at)asrinbilisim(dot)com(dot)tr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jaime Casanova <systemguards(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature freeze date for 8.1
Date: 2005-05-02 09:12:40
Message-ID: web-96002174@mail3.doruk.net.tr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Mon, 02 May 2005 00:25:33 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Jaime Casanova <systemguards(at)gmail(dot)com> writes:
>> Actually, i can't see what's the problem. :)
>
>I think the issue is "how long does it take for the
>rollback to happen?"
>
> ....so I'll beat up on the database people to override
'em instead. Perhaps the database people don't know the
issues and can be browbeaten more easily."

Never, How can ppl change TCP timeouts because PostgreSQL
can run on different OS. I dont want to browbeat you. All
thing i want is to provide a good mechanism to slove this
problem on PostgreSQL like others databases etc. Oracle,
MSSQL, PervasiveSQL and so...

Adnan DURSUN
ASRIN Bilişim Hiz.Ltd.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Hallgren 2005-05-02 09:13:21 Re: custom guc vars
Previous Message Magnus Hagander 2005-05-02 09:12:05 Using LDAP for authorization

Browse pgsql-patches by date

  From Date Subject
Next Message adnandursun 2005-05-02 09:36:41 Re: Feature freeze date for 8.1
Previous Message adnandursun 2005-05-02 08:58:04 Re: Feature freeze date for 8.1