Oliver Jowett <[EMAIL PROTECTED]> writes:
> What do we do if setTransactionIsolation() is called halfway through a
> transaction?
You can't change the isolation status of an already-started transaction
(both Postgres and the SQL spec agree on this). So to the extent that
the user expects this to
"Robert Green" <[EMAIL PROTECTED]> writes:
> I have noticed that using postgresql 7.4.2 at serializable level it is
> possible for two users to update the database at the same time.
I ran your test program here and tracked down what the problem is.
What's happening is that the JDBC driver is issui
Martin Pitt <[EMAIL PROTECTED]> writes:
> In short it was requested to limit the depth of (recursive) function
> calls to prevent database crashes.
http://archives.postgresql.org/pgsql-committers/2004-03/msg00249.php
regards, tom lane
---(end of br
Martin Pitt wrote:
> Hi PostgreSQL hackers!
>
> We recently received and discussed a Debian bug report agains
> postgresql. If you have time, please have a look at
>
> http://bugs.debian.org/239811
>
> In short it was requested to limit the depth of (recursive) function
> calls to prevent data
Name: Rob Green
e-mail: [EMAIL PROTECTED]
PostgreSQL version: 7.4.2
Java version: 1.4.1.03
Operating System: HP-UX 11.00
Host Machine: HP N4000-44 (Quad processor)
Short Description:
Serializable Transactions don't work as well as they did in
postgresql 7.3.3.
I am evaluating tran
Hi PostgreSQL hackers!
We recently received and discussed a Debian bug report agains
postgresql. If you have time, please have a look at
http://bugs.debian.org/239811
In short it was requested to limit the depth of (recursive) function
calls to prevent database crashes. Would it be possible to
I have an ecpg program that runs perfectly on Linux (PostgreSQL 7.4.1). I
recompile it on Solaris and when I try to run there is absolutely no error
handling available. When I connect:
EXEC SQL WHENEVER SQLERROR GOTO sql_error;
EXEC SQL CONNECT TO :dbTarget USER :user USING :pw;
hi,
PostgreSQL Bugs List wrote:
The following bug has been logged online:
Bug reference: 1112
Logged by: Ulf Mehlig
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Debian Linux/i386 "testing"
Description:round(float-type does not work)
D
I added a bunch of print statements in ecpglib/* and it appeared that
ECPGraise is being called, but is writing to the wrong memory location.
Then I noticed compile warnings that "-pthread" is an invalid parameter. It
appears configure is improperly writing config.status. In config.status I
see:
Hi PostgreSQL hackers!
A while ago we received the bug report below against pg_autovacuum.
Since it runs as a daemon, it should detach from its controlling
terminal by executing sth like
int nullfd = open("/dev/null", O_RDWR);
dup2(nullfd, 0);
dup2(nullfd, 1);
dup2
Tom Lane wrote:
> Looking at the code, this seems to be intentional, because the
> privilege check is not made for revokes only for grants:
> Peter, do you remember why you did it that way?
I'm not really sure right now. It doesn't really make sense, does it?
Certainly, the SQL standard require
your name is wrong
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
12 matches
Mail list logo
