The following bug has been logged online:
Bug reference: 2676
Logged by: Luke McFarlane
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Mandriva Linux 2006.0 Kernel 2.6.15.7 SMP
Description:postmaster using 100% cpu from odbc disconnect
Tom
Yes, that does indeed work.
It's interesting why addition assumes one operand is interval while
subtraction assumes it is timestamp? It should at least be consistent, IMHO.
Cheers
Luke
Tom Lane wrote:
Luke McFarlane <[EMAIL PROTECTED]> writes:
SELECT create_time, create_time -
Hello
Given the following example table:
CREATE TABLE foo ( create_time TIMESTAMP WITHOUT TIME ZONE );
INSERT INTO foo (create_time) VALUES (now());
INSERT INTO foo (create_time) VALUES (now());
INSERT INTO foo (create_time) VALUES (now());
This select statement works:
SELECT create_time, create_ti
L' space (for these modes anyway).
Michael Meskes wrote:
On Tue, Jul 06, 2004 at 03:49:14PM +1000, Luke McFarlane wrote:
When defining a symbol on the command line with ecpg -D SYMBOL the ecpg
preprocessor will replace that symbol with empty space in 'C' program
space rather
Hi
I'm running postgresql 7.4.1 and ecpg 3.1.0.
When defining a symbol on the command line with ecpg -D SYMBOL the ecpg
preprocessor will replace that symbol with empty space in 'C' program
space rather than limiting it to 'SQL' program space.
For example:
EXEC SQL IFDEF SYMBOL;
EXEC SQL ...
EXE
