Re: [BUGS] BUG #2665: VC++ 8 (Visual Studio 2005)

2006-10-02 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Uh, I think we still do have reasons to test if we are using MSVC or > > Borland C. I think the #define should just be moved up in c.h. > > Current evidence says otherwise --- but if you insist, why not put the > define in win32.h in

Re: [BUGS] BUG #2665: VC++ 8 (Visual Studio 2005)

2006-10-02 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Uh, I think we still do have reasons to test if we are using MSVC or > Borland C. I think the #define should just be moved up in c.h. Current evidence says otherwise --- but if you insist, why not put the define in win32.h in the first place, instead of

Re: [BUGS] BUG #2665: VC++ 8 (Visual Studio 2005)

2006-10-02 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Interesting. We have inline redefined in src/include/port/win32.h. Can > > you find out why you are not getting those redefined? > > AFAICS, all the "#ifdef WIN32_ONLY_COMPILER" code in win32.h is dead > code, because c.h doesn't #d

Re: [BUGS] BUG #2665: VC++ 8 (Visual Studio 2005)

2006-10-02 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Interesting. We have inline redefined in src/include/port/win32.h. Can > you find out why you are not getting those redefined? AFAICS, all the "#ifdef WIN32_ONLY_COMPILER" code in win32.h is dead code, because c.h doesn't #define WIN32_ONLY_COMPILER un

Re: [BUGS] BUG #2665: VC++ 8 (Visual Studio 2005)

2006-10-02 Thread Bruce Momjian
Oliver Artelt wrote: > > The following bug has been logged online: > > Bug reference: 2665 > Logged by: Oliver Artelt > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.2 beta 1 > Operating system: WinXP + SP2 > Description:VC++ 8 (Visual Studio 2005) > Detail

Re: [BUGS] BUG #2658: Query not using index

2006-10-02 Thread Bruno Wolff III
This shouldn't have been submitted to the bugs list, as it isn't a bug. The best spot for this kind of question is the performance list so I am copying it there and redirecting followups there. On Wed, Sep 27, 2006 at 20:56:32 +, Graham Davis <[EMAIL PROTECTED]> wrote: > > SELECT assetid, m

[BUGS] Mail Delivery (failure [EMAIL PROTECTED])

2006-10-02 Thread pgsql-bugs
---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [BUGS] BUG #1931: ILIKE and LIKE fails on Turkish locale

2006-10-02 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Has this been addressed? Yes, at least as far as we can take it given the current locale infrastructure. There doesn't seem any reasonable way to get regex locale-dependent character classes to work for multibyte chars :-( regar

Re: [BUGS] BUG #1931: ILIKE and LIKE fails on Turkish locale

2006-10-02 Thread Bruce Momjian
Has this been addressed? --- Tom Lane wrote: > Victor Snezhko <[EMAIL PROTECTED]> writes: > > My FreeBSD lists a whole heck of characters: > > > character 0x85 is a space > > character 0xa0 is a space > > character 0xaa is

Re: [BUGS] BUG #2666: how do cluster with 7.4.13 ?

2006-10-02 Thread Jim C. Nasby
On Sat, Sep 30, 2006 at 03:45:09AM +, how to cluster wrote: > > The following bug has been logged online: > > Bug reference: 2666 > Logged by: how to cluster > Email address: [EMAIL PROTECTED] > PostgreSQL version: 7.4.13 > Operating system: i586 > Description:how

Re: [BUGS] Update using sub-select table in schema

2006-10-02 Thread Tom Lane
I wrote: > The comments for refnameRangeTblEntry indicate that at one time we > thought we saw support for our approach in the spec: Here is the discussion thread that settled on our current behavior: http://archives.postgresql.org/pgsql-hackers/2002-03/msg00403.php It looks like we followed Oracl

Re: [BUGS] Update using sub-select table in schema

2006-10-02 Thread Tom Lane
Simon Riggs <[EMAIL PROTECTED]> writes: > On Mon, 2006-10-02 at 11:38 -0400, Tom Lane wrote: >> Postgres treats "FROM temp.a" the same as "FROM temp.a AS a", > [Which AFAICS doesn't follow SQL:2003, since a reference to temp.a > should not be allowed following its redefinition as a.] I'm sorry, I

Re: [BUGS] Update using sub-select table in schema

2006-10-02 Thread Simon Riggs
On Mon, 2006-10-02 at 11:38 -0400, Tom Lane wrote: > Chris Dunlop <[EMAIL PROTECTED]> writes: > > I'm not sure if this is a bug or if it's displaying my ignorance > > of this corner of SQL... > > > update a set name = ( > > select name > > from temp.a > > where temp.a.id = a.id > > ) > > Po

Re: [BUGS] Update using sub-select table in schema

2006-10-02 Thread Tom Lane
Chris Dunlop <[EMAIL PROTECTED]> writes: > I'm not sure if this is a bug or if it's displaying my ignorance > of this corner of SQL... > update a set name = ( > select name > from temp.a > where temp.a.id = a.id > ) Postgres treats "FROM temp.a" the same as "FROM temp.a AS a", and then the

[BUGS] Update using sub-select table in schema

2006-10-02 Thread Chris Dunlop
G'day all, PG version: 8.1.4 (also 7.4.13) OS: Linux (debian/testing) In an update, using a sub-select from a table with the same name but in a different schema results in an error. The same thing works if you alias the sub-select table or if you qualify the schema of the update table. See scr