Richard Broersma Jr <[EMAIL PROTECTED]> writes:
> It seems that 'infinity' still can't be casted to a date. :-(
It's still on the TODO list.
regards, tom lane
---(end of broadcast)---
TIP 3: Have you checked our extensive FA
I am getting a little confused in casting 'infinity'.
It seems that 'infinity' still can't be casted to a date. :-(
But I tried the following casts, but I am not sure the results are consistent.
instrumentation=> SELECT 'infinity'::date;
ERROR: invalid input syntax for type date: "infinity"
i
Thanks if you started to look into this, but nevermind. I figured it
out. Turns out I only needed to mark the function as STABLE:
http://www.postgresql.org/docs/8.0/static/xfunc-volatility.html
"A STABLE function cannot modify the database and is guaranteed to
return the same results given t
All,
I have a weird situation where my index IS used when I use a query that
hard-codes a value but it does NOT use the index when the value is
returned from a PGSQL function:
==
DOES NOT WORK
I realize this is a pgAdmin question but I figure most of you use it and
could help. I've executed the following code:
CREATE TYPE cart_saved_product AS
(
product_id INTEGER,
name VARCHAR(50),
price NUMERIC(10, 2)
);
it created successfully but I do not see it in the pgAdmin ob
Hello,
About a week ago I got a VPS from a web host. The VPS is running
CentOS 5.1. I'm a software developer, new to Postgres and only have
basic Unix admin skills.
I asked the web host to make sure that Postgres is installed. They
did this by running the following command:
yum -y install p
On Fri, 2007-12-28 at 12:33 -0300, marcelo Cortez wrote:
> i received the follow message from backend ,it's this
> a bug?
...
> *** glibc detected *** postgres: postgres richelet
> 201.235.11.133(2504) SELECT: double free or corruption
> (!prev): 0x0845d7e8 ***
> === Backtrace: =
I was also thinking about adding a 'is_new' column to the table which I
would flag as 0, then do a basic copy of all the new rows in with is_new at
1. I'd then do a delete statement to delete all the rows which are
duplicate and have a flag of 0 as the copy should leave me some with two
rows, one
On 31/12/2007 15:07, Abraham, Danny wrote:
runs for about 200s on Postgres, but 13s on MS SQL Server, on the same
machine.
The searched column is indexed.
By reading the "explain" you can tell that the index is being used.
Have you been running VACUUM on the table?
Ray.
-
Hi,
The following query
SELECT START_DATE_IDX, COUNT(*)
FROM RUNINFO_HISTORY
WHERE START_DATE_IDX>=1005
group by START_DATE_IDX
runs for about 200s on Postgres, but 13s on MS SQL Server, on the same
machine.
The searched column is indexed.
By reading the "explain" you can tell that the ind
Hi,
We are running PostgreSQL 8.2.5 on amd64-portbld-freebsd6.2. We have 2
databases, one is a small one (and the pg_dump works ok) and the other one with
14,553,106 rows (the larget table has 3,700,000 rows).
Every day we run a Windows Programmed pg_dump, it used to work fine with
PostgreSQL 8.
11 matches
Mail list logo
