On Sat, Feb 16, 2013 at 10:30:44AM -0800, Kevin Grittner wrote:
- David Kerr wrote:
-
- > Also, if anyone else stumbles upon this, it only seems to happen with jruby.
-
- > I have standard ruby programs where this does not occur.
-
- It sounds like it is at least possible that it is the issue I
David Kerr wrote:
> Also, if anyone else stumbles upon this, it only seems to happen with jruby.
> I have standard ruby programs where this does not occur.
It sounds like it is at least possible that it is the issue I described here:
http://www.postgresql.org/message-id/4afbe87202250002c..
On Fri, Feb 15, 2013 at 07:01:20PM -0600, Ren Romero Benavides wrote:
- I can confirm it comes from pgpool, and is very weird , I guess the pgpool
list
- would be a better fit.
- Cheers.
hmm, ok thanks I'll post there as well.
Also, if anyone else stumbles upon this, it only seems to happen wit
I can confirm it comes from pgpool, and is very weird , I guess the pgpool list
would be a better fit.
Cheers.
On Friday, February 15, 2013 01:58:55 PM David Kerr wrote:
> Howdy!
>
> This query is coming from PgPool I believe.
>
> SELECT count(*) FROM pg_catalog.pg_class AS c WHERE c.relname =
Howdy!
This query is coming from PgPool I believe.
SELECT count(*) FROM pg_catalog.pg_class AS c WHERE c.relname = 'import_jobs'
AND c.relpersistence = 'u'
This is a very small database, like 10/15 tables, it's basically empty.
If i run this query manually, it comes back immediatly.
However
