> You need to recast the clause as something like
>
> WHERE posted >= (CURRENT_TIMESTAMP - '5 minutes'::TIMESPAN)
>
> Then you still have the problem of persuading Postgres that it should
> treat the right side of this as a constant and not something to
> re-evaluate at each row. In 7.0 a
Itai Zukerman <[EMAIL PROTECTED]> writes:
> I have this:
> SELECT ...
> FROM trade, entry
> WHERE AGE( CURRENT_TIMESTAMP, posted ) <= '5 minutes'::TIMESPAN
> AND trade.entryId = entry.entryId
> That is, fetch all trades executed in the last 5 minutes.
> This query seems
I have this:
SELECT ...
FROM trade, entry
WHERE AGE( CURRENT_TIMESTAMP, posted ) <= '5 minutes'::TIMESPAN
AND trade.entryId = entry.entryId
That is, fetch all trades executed in the last 5 minutes.
This query seems to run pretty slowly when trade is filled. Putting
an
