When I insert to table new row and after this
in the same transaction I delete this row I get such error: triggered data
change violation on relation "tbl_b"
I've created database using simple
script:
CREATE TABLE tbl_a(
pn_id SERIAL,
pn_a VARCHAR(400) NOT NULL, PRIMARY KEY
You cannot insert and delete the same data within one transaction.
Only one change of a row is allowed.
Greetings
Andreas
On Wed, 29 Aug 2001 13:18:02 +0200
"Pawel Pawlowski" <[EMAIL PROTECTED]> wrote:
> When I insert to table new row and after this in the same transaction I delete this
>row I
Im changing now database from Interbase 6.0 to PosgreSql 7.1.2. With IB
there is no problem to do such things.
This problem only exist when I create table tbl_a with references
(REFERENCES tbl_a (pn_id) ON UPDATE CASCADE ON DELETE CASCADE). Without this
part everything works OK. So I think that pr
Hi, sorry if is a know bug but I have -1 second to check it.
Problem:
I add the plpgsql language
I insert a plpgsql function with a script file (psql < or psql -f )
I drop this function with the same script
this drop fails
If I start psql in interactive mode and drop the funct
Hi,
I found a case where psql 7.1.3 doesn't use indices when the number of
rows is very large.
In the FIRST SESSION (below) I create the table foo and fill it with
200 rows. Then, I create an index in the 'bar' field and run some
explains and they all return 'Index Scan'. So far, everything is
I attempted to load data amounting to 21 mbytes into a table which has
a unique key both otherwise doesn't have indexes.
The WALs consumed 2.9 Gigabytes of disk (and doubtless would have taken
more if there was more to be had).
Considering that the entire data would fit into RAM (I have 128
If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to [EMAIL PROTECTED]
To report any other bug, fill out the form below and e-mail it to
[EMAIL PROTECTED]
If you not only found the proble
Title: Roger Waters w Polsce
Roger Waters w Polsce!
http://ton.poland.com
I'm getting the following error from my application log file. I'm using
Postgres 7.1.2 running on HP-UX 11.0. These errors are results from our
Java servlet programs using the postgresql driver:
"Something unusual has occured to cause the driver to fail.
Please report this exception: java.sql
This was a mistake in the interpretation of the spec (modification of
the same key row referenced by a foreign key constraint in the same
statement more than once is an error is how we believe the spec meant
it, but there's a case where they mention transaction and it got
misinterpreted). I don'
You probably need to run vacuum analyze after filling in the data.
Otherwise it's using bogus selectivity (see the number of expected
rows returned by the explain output, it's expecting 6000 rows after
the create index, which is large enough to make it guess that
it'll be cheaper to sequence scan
> Please enter a FULL description of your problem:
>
>
> Our development server, on occaision, runs out of swap space and
> inevitably when it does, the postmaster process stops. When restarted,
> the following info is in the log (the machine ran
Sorry about that, things are never as easy as they seem. The answer appears
to be to filter PG_Stream.java in a similar manner as is done to Driver.java
Attached please find two files.
1) diffs for build.xml.
2) PG_Stream.java.in
I hope this can now be put to bed.
David Daney.
Bruce Mom
13 matches
Mail list logo
