Hi
PG_RETURN_TEXT_P works well. I made beginer error. I allocated memory by
palloc and before PG_RETURN_TEXT_P deallocated by SPI_finish. After change
SPI_palloc between palloc my function works.
Thank you
Pavel
On Tue, 12 Nov 2002, Pavel Stehule wrote:
> You have true. When I modify code on
Paul Mamin ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Bad time conversion from type abstime to datetime
Long Description
After making query (in psql):
select '2002-11-12 15:02:05'::abstime::datetime;
timestamp
---
MI ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Valid timezone +1300 rejected
Long Description
New Zealand Daylight Savings Time time zone is "+1300" (and others as well, I think).
Silly, I agree, but that's how it is.
Postg
[EMAIL PROTECTED] writes:
> select '2002-11-12 15:02:05'::abstime::datetime;
> timestamp
> -
> 2002-11-12 05:02:05
> (1 row)
Seems to be fixed in 7.3.
regards, tom lane
---(end of broadcast)---
TIP
[EMAIL PROTECTED] writes:
> Valid timezone +1300 rejected
Hm, this was reported before but didn't get fixed. I've now fixed it
for 7.3. It's a one-word change in DecodeTimezone() in
src/backend/utils/adt/datetime.c, if you want to patch your 7.2.
regards, tom lane
-
Using postgres 7.2.3 the query planner seems to lose interest in using
indexes when DISTINCT is used.
Sample query without DISTINCT:
SELECT
ps_7.id,
FROM
ps_7,
page
WHERE
page.id = ps_7.id
ORDER BY
ps_7.id DESC
LIMIT 5;
NOTICE: QUERY PLAN:
Limit (cost=0.00..33.22 rows=5 width=16)
