Re: [SQL] Sql select like question.

2005-05-26 Thread hatuan
My version is PostgreSQL 8.0.3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special) - Original Message - From: Tom Lane [EMAIL PROTECTED] To: hatuan [EMAIL PROTECTED] Cc: pgsql-sql@postgresql.org Sent: Thursday, May 26, 2005 4:19 AM Subject: Re: [SQL] Sql select like

[SQL] unsubscribe

2005-05-26 Thread U K Laxmi
__ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/ ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ?

Re: [SQL] Sql select like question.

2005-05-26 Thread Tom Lane
hatuan [EMAIL PROTECTED] writes: My version is PostgreSQL 8.0.3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special) Well, if it's 8.0.3 then you've found a new variant of the problem, but we cannot fix it without a complete test case. Please read the bug reporting

Re: [SQL] Sql select like question.

2005-05-26 Thread hatuan
I have fixed it. I have pg8.03 but database is 8.0. I dump database and reload it, it work well. Thank for your help. - Original Message - From: Tom Lane [EMAIL PROTECTED] To: hatuan [EMAIL PROTECTED] Cc: pgsql-sql@postgresql.org Sent: Thursday, May 26, 2005 4:19 AM Subject: Re: [SQL] Sql

Re: [SQL] Duplicated records

2005-05-26 Thread Andrew Hammond
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Thanks CTAS (Create Table As Select) command works fine!!! With great performance. I think it is the best way to correct the data...(apparently) I didnt know about select DISTINCT. I am going to read about it. You

[Fwd: [SQL] unsubscribe]

2005-05-26 Thread noor
Original Message Subject: [SQL] unsubscribe From:U K Laxmi [EMAIL PROTECTED] Date:Thu, May 26, 2005 1:52 pm To: hatuan [EMAIL PROTECTED] Tom Lane [EMAIL PROTECTED] Cc:

Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {}

2005-05-26 Thread Joe Conway
Tom Lane wrote: I think he's got a good point, actually. We document the ARRAY-with- parens-around-a-SELECT syntax as The resulting one-dimensional array will have an element for each row in the subquery result, with an element type matching that of the subquery's

[SQL] 3 tables, slow count(*), order by Seq Scan in Query Plan

2005-05-26 Thread ogjunk-pgjedan
Hello, I have 3 tables (2 tables + 1 lookup table that ties them) and running a straight-forward aggregate count(*) query with a couple of joins takes about 10 seconds (and I need it to be sub-second or so). Also, I am wondering if this approach is scalable with my row-counts and my hardware