Em Sunday 11 November 2007 04:51:20 rihad escreveu:
> pre-hydration, too. This all resulted in much effort not directly
> related to the business logic of my app, but rather on overriding
> Symfony's way of doing everyday web-programming tasks (like form
> validation, results listing, editing). Now
Tom Lane wrote:
=?ISO-8859-1?Q?Christian_Schr=F6der?= <[EMAIL PROTECTED]> writes:
Although I do not yet have any processes that are stuck inside a
statement, there are some that are idle, but do not respond to SIGINT or
even SIGTERM. Is this sufficient?
Dunno. Have you looked at thei
On Sun, Nov 11, 2007 at 06:34:40PM +0100, Christian Schröder wrote:
> I recompiled the server with debugging symbols enabled and then did the
> following experiment: I started a query which I knew would take some
> time. While the query executed I disconnected my dial-up line. After
> reconnecti
=?ISO-8859-1?Q?Christian_Schr=F6der?= <[EMAIL PROTECTED]> writes:
> (gdb) bt
> #0 0x2b24aeee0a68 in __lll_mutex_lock_wait () from
> /lib64/libpthread.so.0
> #1 0x2b24aeedde88 in pthread_rwlock_rdlock () from
> /lib64/libpthread.so.0
> #2 0x2b24a5814e23 in _nl_find_msg () from /lib6
Tom Lane wrote:
I recompiled the server with debugging symbols enabled and then did the
following experiment: I started a query which I knew would take some
time. While the query executed I disconnected my dial-up line. After
reconnecting the backend process was still there (still SELECTing).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
just compiled a fresh 8.3 on my Ubuntu Gutsy, but there's one thing
which seems to have changed though I cannot get any hint about that in
the docs:
Given a table bla(a bigint,b text)
select * from bla where a like '8%'
works in <=8.2, but not
On Nov 11, 2007, at 18:46 , Patric Bechtel wrote:
Given a table bla(a bigint,b text)
select * from bla where a like '8%'
works in <=8.2, but not on 8.3
Same happens with date columns, too.
The server is now more strict and has fewer implicit type casts in
8.3, so this is working as inten
Hi:
How user specific is pg_tables when it comes to temporary tables? It
seems to pick up the existence of a a temp table created by the same
user but a different session. Here's the demo scenario
Session 1:
mydb=# create temporary table foo (a int);
Session 2:
stdb2=# select tab
I wrote a headline generation function for my app and I have attached
the patch (against the cvs head). It generates multiple contexts in
which the query appears. Essentially, it uses the cover function to
generate all covers, chooses smallest covers and stretches each
selected cover according to t
