On Fri, Jan 20, 2006 at 11:47:55PM -0500, Tom Lane wrote:
> Alfranio Correia Junior <[EMAIL PROTECTED]> writes:
> > What could cause the status ("select waiting") ?
>
> Perhaps you are using SELECT FOR UPDATE?
or SELECT func_with_side_effects() ?
-Mike
---(end of broad
This would be handy for testing high-concurrency workloads.
http://blogs.sun.com/roller/page/jonathan/20051218
-Mike
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
On Sun, Aug 21, 2005 at 09:13:20PM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > What do people think of exposing pg_usleep() to the user?
>
> I'm not real enthused about it. Generally speaking, a sleep() on the
> database side means you are idling while holding locks, and
On Mon, Mar 14, 2005 at 02:53:36AM -0500, Tom Lane wrote:
> Probably the first thing to do is look around at the plausible users of
> this thing and see what they'd find most convenient.
This may be totally irrelevant:
Our current load distributors, like pgpool, have no way of knowing the
side ef
On Wed, Mar 02, 2005 at 07:21:41AM -0800, Mark Wong wrote:
> Ah, ok. I've reapplied the 2Q patch to CVS from 20050301:
> http://www.osdl.org/projects/dbt2dev/results/dev4-010/313/
>
> I ran it for 3 hours, just in case, and the charts suggest it flattens
> out after 2 hours.
Looking at the
On Tue, Feb 15, 2005 at 08:03:39PM +0300, E.Rodichev wrote:
> On Tue, 15 Feb 2005, Magnus Hagander wrote:
> >Question 1: Is your writeback cache really disabled in Linux, on the
> >harddrive? Windows fsync will *write through the disk write cache* if
> >the driver is properly implemented. AFAIK, on
On Tue, Jan 25, 2005 at 03:29:55PM -0800, Dann Corbit wrote:
> If you store the temp tables in RAM, how will you preserve the ACID
> property on power failure (without using write-through which would
> negate the speed advantage)?
>
> The temp tables may be participating in a transaction.
Temp ta
(only tangentally on topic)
Interesting tail on the problems of MyISAM tables, disk write-caching,
and sharing space with people who can't resist pushing the big red
button. Only tangentally on topic.
http://www.livejournal.com/community/lj_dev/670215.html
I wonder what livejournal would look l
On Thu, Sep 30, 2004 at 09:45:51AM -0400, Merlin Moncure wrote:
> Now, if the same query is executed as a prepared statement,
> prepare ps(...) as select f(t.c) from t where [expr] limit 1;
> execute ps;
>
> now, if ps ends up using a index scan on t, everything is ok. However,
> if ps does a seq
