Ah, I see what you mean. If there's no rows to return, then there's no
coalesce-ing to do...
sorry for the spam.
--Richard
On Jul 14, 2010, at 5:12 PM, Thom Brown wrote:
> On 15 July 2010 00:52, Richard Yen wrote:
>> Hi everyone,
>>
>> Looks like I&
Hi everyone,
Looks like I'm encountering some quirks with coalesce()...
> postgres=# select coalesce(null,0);
> coalesce
> --
> 0
> (1 row)
>
> postgres=# SELECT COALESCE(ROUND(EXTRACT(epoch FROM now()-query_start)),0)
> FROM pg_stat_activity WHERE current_query = ' in transac
Hi All,
I encountered an odd issue regarding check constraints complaining
when they're not really violated.
For this particular machine, I am running 8.3.7, but on a machine
running 8.3.5, it seems to have succeeded. I also upgraded a third
machine from 8.3.5 to 8.3.7, and the query succeeded (
在 Feb 9, 2009 8:52 PM 時， Tom Lane 寫到：
Richard Yen writes:
It seems like all the deadlocks are for tuple (3,60), but strangely,
tuple (3,60) on the account table doesn't exist. Perhaps it was
deleted? According to the account table, the account with id = 39271
(which the UPDATE state
Hi,
I'm trying to make sense of a situation I ran into this morning.
Apparently, there were numerous deadlocks (approx. 75 in a 30-min
period) while procs were trying to write to a table (16634, "account")
in my database.
Just to give you a sense of what's going on, process 22583 tried t
Hi, I'm trying to create a dumpfile for a client. The data is
gathered from about 7 tables, and I need to output all the columns as
the client wishes.
I figure the best way to this is to collect data from multiple tables
and putting them into a view, and using the client's desired names to
Hi all,
I'm experiencing signal 11 (segmentation fault) failures on the
master node of a 3-node Slony-I cluster. In the past week, we've
averaged a little more than one segfault per day (11 times in the
past 10, including today). Any ideas what's going on?
Would anyone know how to track
