From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Rhaoni Chiu Pereira <rhaoni(at)sistemica(dot)info> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: How to force an Index ? |
Date: | 2003-09-18 18:02:10 |
Message-ID: | 200309181102.10288.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
Rhaoni,
> I could .. but this way I wont be used because Oracle doesn't accept such
> sintax ! I changed gsames00.ano_mes from varchar to text ! But it still not
> fast enough to take Oracle's place !!!
> I still trying to do so ...
Well, your basic problem is that performance tuning for *any* database often
requires use of database-specific syntax. You would be having the same
problem, in the opposite direction, if you were trying to port a PostgreSQL
app to Oracle without changing any syntax.
Here's syntax Oracle should accept:
... gsames00.ano_mes = (CAST(to_char(ftnfco00.data_emissao,'YYYYMM') AS
VARCHAR)) AND
...
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Gustavo Pérez | 2003-09-18 20:26:48 | varchar too long strange problem |
Previous Message | Josh Berkus | 2003-09-18 17:50:34 | Re: [PERFORM] How to force an Index ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-09-18 18:20:33 | Re: Many fields in one table or many tables? |
Previous Message | Joseph Bove | 2003-09-18 18:01:05 | Find one record |