Re: Open 7.1 items

From: "Constantin S(dot) Svintsoff" <cs(at)newst(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Open 7.1 items
Date: 2001-01-28 08:04:04
Message-ID: Pine.BSF.4.21.0101281346270.38806-100000@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi, there!

On Sat, 27 Jan 2001, Bruce Momjian wrote:

> Here are the open items for 7.1. Much shorter:
>
> Reorder INSERT firing in rules
> JDBC LargeObject short read return value missing
> LAZY VACUUM
> JDBC setMaxRows() is global variable affecting other objects
> Fix for pg_dump of bad system tables
> ODBC not disconnecting properly?
> Magnus Hagander ODBC issues?
> Merge MySQL/PgSQL translation scripts
> Fix ipcclean on Linux
> unixODBC
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>

What about strange write locking of primary index element, if something
that references it is changed (inserted or updated), you cannot modify
in other transaction something else that references the same primary
index element until first transaction ends. For example:

CREATE table primtest (id integer primary key);

CREATE table foreigntest1 (id integer references primtest);

CREATE table foreigntest2 (id integer references primtest);

INSERT INTO primtest VALUES (1);

BEGIN;

INSERT INTO foreigntest1 VALUES (1);

-- and in other transaction:

INSERT INTO foreigntest2 VALUES (1);

-- blocked until COMMIT or ROLLBACK issued in first transaction.

/Constantin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= 2001-01-28 17:49:20 Re: Re: Sure enough, the lock file is gone
Previous Message Oliver Elphick 2001-01-28 07:57:43 Re: Re: [GENERAL] MySQL -> Postgres dump converter