Re: [GENERAL] index not always used when selecting on a date field

2004-11-10 Thread "Miquel van Smoorenburg"
In article <[EMAIL PROTECTED]>, Tom Lane <[EMAIL PROTECTED]> wrote: >[EMAIL PROTECTED] ("Miquel van Smoorenburg" ) writes: >> techdb2=> explain select * from lines where (removed > CURRENT_DATE >AND removed < '-01-01'); > >>

Re: [GENERAL] index not always used when selecting on a date field

2004-11-08 Thread &quot;Miquel van Smoorenburg"
In article <[EMAIL PROTECTED]>, Greg Stark <[EMAIL PROTECTED]> wrote: > >Russell Smith <[EMAIL PROTECTED]> writes: > >> now() and CURRENT_DATE, are and cannot be planned as constants. >> So the planner cannot use an index for them. > >It's not that it cannot use an index, but that it doesn't know

[GENERAL] index not always used when selecting on a date field

2004-11-07 Thread &quot;Miquel van Smoorenburg"
I have a database with a btree index on the 'removed' field, which is of type 'date'. However it isn't being used: techdb2=> explain select * from lines where removed > CURRENT_DATE; QUERY PLAN Seq Scan on lines

Re: [GENERAL] Humor me: Postgresql vs. MySql (esp. licensing)

2003-10-16 Thread Miquel van Smoorenburg
In article <[EMAIL PROTECTED]>, John Wells <[EMAIL PROTECTED]> wrote: >Here's an interesting response from mysql.com sales. Frankly, I don't see >how using it on multiple internal servers violates the GPL?!?: You're talking to a sales droid, a suit, someone whose brain cells have died off because

Re: [GENERAL] PostgreSQL upgrade -> fails to start server

2003-08-29 Thread Miquel van Smoorenburg
In article <[EMAIL PROTECTED]>, Sander Smeenk <[EMAIL PROTECTED]> wrote: >Hi, > >After a very recent postgresql update, the postmaster failed to start >because of this: > >| PANIC: The database cluster was initialized with LC_CTYPE >| '[EMAIL PROTECTED]', which is not recognized by setlo