| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Hannu Krosing" <hannu(at)tm(dot)ee> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "PostgreSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org>, "Didier Moens" <moensd(at)xs4all(dot)be> |
| Subject: | Re: Foreign key wierdness |
| Date: | 2003-01-20 17:04:41 |
| Message-ID: | 03AF4E498C591348A42FC93DEA9661B8259AE6@mail.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Hannu Krosing [mailto:hannu(at)tm(dot)ee]
> Sent: 20 January 2003 18:05
> To: Dave Page
> Cc: Tom Lane; PostgreSQL Hackers Mailing List; Didier Moens
> Subject: Re: [HACKERS] Foreign key wierdness
>
>
> > I've been looking at his for some time now (couple of weeks
> or more),
> > and the only thing I can find is the SELECT ... FOR UPDATE in the
> > PostgreSQL logs that I quoted.
>
> does this SELECT ... FOR UPDATE occur only when schemas are used ?
No, in both case, just significantly more slowly with schema
qualification. Note that the qualification is added to the ALTER TABLE
statement though - PostgreSQL's qualifying the name in the SELECT for
every case.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2003-01-20 18:05:17 | Re: Foreign key wierdness |
| Previous Message | Dave Page | 2003-01-20 17:01:46 | Re: Foreign key wierdness |