Re: [HACKERS] Comments from a Firebird user via Borland Newsgroups.

2005-11-10 Thread Tony Caduto
Tom Lane wrote: http://candle.pha.pa.us/main/writings/pgsql/sgml/sql-set-transaction.html http://candle.pha.pa.us/main/writings/pgsql/sgml/transaction-iso.html It's a bit amusing that this person is dissing us for not having REPEATABLE READ, when what he actually seems to want is

Re: [HACKERS] Comments from a Firebird user via Borland Newsgroups.

2005-11-10 Thread Marc G. Fournier
On Thu, 10 Nov 2005, Tony Caduto wrote: Serializable is stricter and somehwat unusable in a multi-user, loaded database, because only one transaction can run at any time. Let's say you would have one long running serializable transaction encapsulating a reporting query, this will cause other

Re: [HACKERS] Comments from a Firebird user via Borland Newsgroups.

2005-11-10 Thread Tom Lane
Tony Caduto [EMAIL PROTECTED] writes: Tom, This is what the firebird guy said: Serializable is stricter and somehwat unusable in a multi-user, loaded database, because only one transaction can run at any time. He's already demonstrated that he has no clue what he's talking about, so I think

Re: [HACKERS] Comments from a Firebird user via Borland

2005-11-10 Thread Kevin Grittner
Hi Tony, As the referenced documentation states, the PostgreSQL SERIALIZABLE transaction isolation level complies with the ANSI/ISO requirements, but not with a mathematically pure interpretation of the term. (The only quibble I have with that documentation is that you have to be averting your

Re: [HACKERS] Comments from a Firebird user via Borland

2005-11-10 Thread Bruno Wolff III
On Thu, Nov 10, 2005 at 12:00:12 -0600, Kevin Grittner [EMAIL PROTECTED] wrote: Hi Tony, As the referenced documentation states, the PostgreSQL SERIALIZABLE transaction isolation level complies with the ANSI/ISO requirements, but not with a mathematically pure interpretation of the term.

[HACKERS] Comments from a Firebird user via Borland Newsgroups.

2005-11-09 Thread Tony Caduto
We found PostgreSQL a mature product, but in two things Firebird was simply better than PostgreSQL: Two-Phase commit (ok, that is gone with PG 8.1), but the second is a SNAPSHOT / REPEATABLE READ transaction isolation. I can't live without that when it comes having a stable view of data during

Re: [HACKERS] Comments from a Firebird user via Borland Newsgroups.

2005-11-09 Thread Rod Taylor
On Wed, 2005-11-09 at 19:35 -0600, Tony Caduto wrote: We found PostgreSQL a mature product, but in two things Firebird was simply better than PostgreSQL: Two-Phase commit (ok, that is gone with PG 8.1), but the second is a SNAPSHOT / REPEATABLE READ transaction isolation. I can't live

Re: [HACKERS] Comments from a Firebird user via Borland Newsgroups.

2005-11-09 Thread Bruno Wolff III
On Wed, Nov 09, 2005 at 19:35:30 -0600, Tony Caduto [EMAIL PROTECTED] wrote: We found PostgreSQL a mature product, but in two things Firebird was simply better than PostgreSQL: Two-Phase commit (ok, that is gone with PG 8.1), but the second is a SNAPSHOT / REPEATABLE READ transaction

Re: [HACKERS] Comments from a Firebird user via Borland Newsgroups.

2005-11-09 Thread Tom Lane
Bruno Wolff III [EMAIL PROTECTED] writes: On Wed, Nov 09, 2005 at 19:35:30 -0600, Tony Caduto [EMAIL PROTECTED] wrote: We found PostgreSQL a mature product, but in two things Firebird was simply better than PostgreSQL: Two-Phase commit (ok, that is gone with PG 8.1), but the second is a