I'm sorry about doing this but I've been haveing problems sending to the list, this is
an atempt to make it work
You can ingnore this and other messages with the same subject
Thanks in advance
\\DarcyB
POSTGRESQL BUG REPORT TEMPLATE
Your name : Darcy
Your email address : [EMAIL
POSTGRESQL BUG REPORT TEMPLATE
Your name : Darcy
Your email address : [EMAIL
Here is an other set of strange bugs I've discovered relateing to dates..
SELECT date_part('day', ('2000-11-1 0:00'::datetime + '-1day'))::int4 AS
days_in_month;
days
31
(1 row)
SELECT date_part('day', (('2000-10-1 0:00'::datetime + '1 month') + '-1
day'))::int4 AS days_in_month;
SEL
let me try this again...
Here is an other set of strange bugs I've discovered relating to dates.
this bug only rears it's head for 1 day a year form what I can find..
october 31'st, the intent of the queries is to get the last day of a month..
SELECT date_part('day', ('2000-11-1 0:00'::date
this happens on FreeBSD 3.5-STABLE, running both 6.5.3 and 7.0.2
as well as FreeBSD 2.28-RELEASE running 6.4.(something)
At 03:52 PM 8/15/00 +1000, you wrote:
>At 22:38 14/08/00 -0700, Darcy Buskermolen wrote:
>>let me try this again...
>>
>>
>>Here is an oth
Could it also be the result of a Cluster operation? I've seen strange
things related to functions/triggers on tables that I've clustered.
>> At a guess, you've run into the known bug that foreign key triggers
>> don't track renames of referenced tables. Did you rename a table that
>> is a forei
Ok this has since been sorted out, however I propose that it is better
layed out in the documentation, or at the veryleast an example is given.
i MUST be defined as a RECORD, and you then refrence the returned result as
RECORD.field, Also you can NOT have ()'s arouns the select statement.
CREATE
type \q to quit
type \g or terminate with semicolon to execute query
You are currently connected to the database: darcy
darcy=> select date_part('dow','april 1, 2001'::date);
date_part
-----
6
(1 row)
darcy=> select date_part('dow','april 2, 20
At 09:58 AM 11/20/01 -0500, you wrote:
>[EMAIL PROTECTED] writes:
>> Using the postgresql TO_CHAR function with Day, DAY, day, Month, MONTH
or month as the text argument, extra whitespace is appended to the output.
>
>AFAIK this is the intended behavior. There's an FM modifier that you
>add to th
This is because user is a "reserved" word.
user is a macro for the function current_user()
Try this SQL: SELECT user;
It is best to change the table name from user to username;
However it is probably a wise idea for Postgres to emit some sort of error
on the create mentioning the reserved word
When useing COPY FROM 'file'
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ACK! must rember which MTA I'm useing...
When useing COPY FROM 'file' DELIMITER '\254' copyfrom reads past the
delimiter and ends up with parse errors when trying to do the insert
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ACK! must rember which MTA I'm useing...
When useing COPY FROM 'file' DELIMITER '\254' copyfrom reads past the
delimiter and ends up with parse errors when trying to do the insert
What the ?? why dind' tthat go through with the body of the text.. *sigh*
I'll resend in the AM..
---
Postgres was not compiled with Multibyte, if I replace the if (delimc == c)
with if (strstr(delim,c)) it works as expected. This changes was
implemented for performance reasons according to the CVS log.
At 11:57 PM 2/25/02 -0500, Tom Lane wrote:
>Darcy Buskermolen <[EMAIL PROTECTED]&g
This patch solves the problem.
At 09:16 PM 2/26/02 +0900, Tatsuo Ishii wrote:
>> When useing COPY FROM 'file' DELIMITER '\254' copyfrom reads past the
>> delimiter and ends up with parse errors when trying to do the insert
>>
>>
>> What the ?? why dind' tthat go through with the body of the tex
The numbers you see are OID'S, ie the OID of the relation. this is done to
prevent name clashing and also makes fo easy lookups by the backend it self.
At 12:18 PM 3/16/02 -0500, you wrote:
>daizhong ([EMAIL PROTECTED]) reports a bug with a severity of 2
>The lower the number the more severe it
e value
> of last_value is 4 before the kill -9 and 34 when it comes back up.
I'm sure if you read the footers on Tom's email's it's pretty clearly stated
'do not kill -9 the postmaster'.
So I'm not so sure that this is really a bug.
--
Darcy Buskermol
econds')::INTERVAL, (9 || ' seconds')::INTERVAL;
interval | interval | interval
-+-+-
24855 days 03:14:07 | 24855 days 03:14:07 | 24855 days 03:14:07
(1 row)
--
Darcy Buskermo
or is there somewhere better to send it?
>
>
> ---(end of broadcast)---
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
--
Darcy Buskermolen
Wavefire Technol
become a DOMAIN of NUMERIC for those converting.
> >
> > --
> > -Josh Berkus
> > Aglio Database Solutions
> > San Francisco
> >
> >
> > ---(end of broadcast)---
> > TIP 6: Have you searched our li
Sorry my mistake on versions.
darcy=> SELECT '1.0'::MONEY::FLOAT;
?column?
1
(1 row)
darcy=> SELECT '1.0'::MONEY::TEXT;
?column?
----
1.0
(1 row)
darcy=&
Tom you are correct here (like usual), sorry for the wasted thread and time
regarding functions that I remembered being there but infact were not.
On Wednesday 29 January 2003 10:56, Tom Lane wrote:
> Darcy Buskermolen <[EMAIL PROTECTED]> writes:
> > Sorry my mistake on vers
= '1186';
1186 ( the interval type) is the only row that this does not work for.
--
Darcy Buskermolen
Wavefire Technologies Corp.
ph: 250.717.0200
fx: 250.763.1759
http://www.wavefire.com
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
---
A A
SQL> select length(value||value) from dummy;
LENGTH(VALUE||VALUE)
----
8
--
Darcy Buskermolen
Wavefire Technologies Corp.
ph: 250.717.0200
fx: 250.763.1759
http://www.wavefire.com
---(end of broadcast)--
t; `pthread_mutex_unlock'
> > > ../../../src/interfaces/libpq/libpq.so: undefined reference to
> > > `pthread_mutex_lock'
>
> No, I think it should work. If it passes the thread tests in configure,
> it should compile. I am unsure why it is failing.
it's m
26 matches
Mail list logo
