correct. Also, if the client is still "alive" they have no effect either.
On Fri, May 29, 2009 at 11:01 AM, Y W wrote:
> I'm sorry that was my bad, they're only ignored when uing Unix-domain
> sockets to connect instead of TCP/IP.
>
> On Fri, May 29, 2009 at 12:55 PM, Y W wrote:
>>
>> But accor
On Fri, May 29, 2009 at 10:55 AM, Y W wrote:
> But according to the documentation, are they ignored if postgres was hosted
> on a Unix/linux system?
They work fine on unix, as long as the user has the option to set
their own timeouts. If not then set them for the OS (for linux see
/etc/sysctl.co
On Fri, May 29, 2009 at 10:18 AM, Y W wrote:
> Are you referring to connection settings ? Coz if u do, the closet thing I
> can find for the tcp_keepalive_timeout u're mentioning are the
> tcp_keepalives_idle, tcp_keepalives_interval, and the tcp_keepalives_count.
> And apart from the fact that th
On Thu, May 28, 2009 at 9:52 PM, Yasser Idris wrote:
>
> Dude, all what u wrote make sense. Only your missing one thing, consider the
> following scenario that u already reply to:
>
>>> For. example: I forget to make commit, or rollback on exception then all
>>> resources I used (updated) is locke
Dude, all what u wrote make sense. Only your missing one thing, consider the
following scenario that u already reply to:
>> For. example: I forget to make commit, or rollback on exception then all
>> resources I used (updated) is locked.
>Yes - that's an application bug.
Even if it's applicati
durumdara wrote:
If set wait and timeout, the Firebird is waiting for the locked resource
(record) for X seconds before it show deadlock error.
But when you set no wait, the deadlock error immediately shown by the
server.
Waiting on a lock doesn't mean there's a deadlock. A deadlock only
o
2009/5/6 Albe Laurenz :
> durumdara wrote:
>> In FireBird the transactions have these settings:
>>
>>
>> SET TRANSACTION
>> [NAME hostvar]
>> [READ WRITE | READ ONLY]
>> [ [ISOLATION LEVEL] { SNAPSHOT [TABLE STABILITY]
>> | READ COMMITTED [[NO] RECORD_VERSION] } ]
durumdara wrote:
> In FireBird the transactions have these settings:
>
>
> SET TRANSACTION
>[NAME hostvar]
>[READ WRITE | READ ONLY]
>[ [ISOLATION LEVEL] { SNAPSHOT [TABLE STABILITY]
> | READ COMMITTED [[NO] RECORD_VERSION] } ]
>[WAIT | NO WAIT]
>[LOCK
Hi!
2009.05.06. 11:54 keltezéssel, Richard Huxton írta:
durumdara wrote:
So: have PGSQL same mechanism like nowait?
When you take a lock:
http://www.postgresql.org/docs/8.3/interactive/sql-lock.html
http://www.postgresql.org/docs/8.3/interactive/sql-select.html#SQL-FOR-UPDATE-SHARE
As I se
Hi!
In FireBird the transactions have these settings:
SET TRANSACTION
[NAME/|hostvar|/]
[READ WRITE | READ ONLY]
[ [ISOLATION LEVEL] { SNAPSHOT [TABLE STABILITY]
| READ COMMITTED [[NO] RECORD_VERSION] } ]
[WAIT | NO WAIT]
[LOCK TIMEOUT/|seconds|/]
And thi
10 matches
Mail list logo
