Ciprian Grigoras wrote:
> Has anyone seen a similar issue (maybe a bug in the 9.0 version ?) where
> simple statements don't finish and get locked there and can't be killed by
> the pg_terminate_backed ? What is the cause of this ?
Interesting. I wonder if you just wrapped around pg_multixact an
On Fri, Apr 29, 2016 at 1:09 PM, John R Pierce wrote:
> On 4/29/2016 10:30 AM, Ciprian Grigoras wrote:
>
> We're running Postgresql 9.0.7...
>
>
> do note, the 9.0 series got up to 9.0.23 before it was discontinued last
> year. 9.0.7 was released in February 2012, 4+ years ago.
>
> 9.0.18 fixed
Thanks everyone, it could be that the Linux server is problematic (it's
got a long uptime).
I ran the strace thing,
1. [root@box ~]# strace -p 20825
2. Process 20825 attached - interrupt to quit
3. connect(90, {sa_family=AF_FILE, path="/var/centrifydc/daemon2"}, 25
and it kept waiting
Ciprian Grigoras writes:
> Hi guys,
>
> I had a question. We're running Postgresql 9.0.7 , and all of a sudden we
> started seeing unexpected behavior. One table got locked after we ran one
> simple INSERT on one
> test item.
> Nothing else was running against that table as far as we know, and
On 4/29/2016 10:30 AM, Ciprian Grigoras wrote:
We're running Postgresql 9.0.7...
do note, the 9.0 series got up to 9.0.23 before it was discontinued last
year. 9.0.7 was released in February 2012, 4+ years ago.
9.0.18 fixed some index corruption bugs in GIST indexes, 9.0.15 fixed a
bunch
Check the wait state for the backend process. I’ve seen this happen when a
process ran a per-row trigger that tried to connect to something else, and it
filled the ip_conntrack table. So, kernel level wait along with a whole bunch
of locks on the table in question.
Running pg_terminate_back
Hi guys,
I had a question. We're running Postgresql 9.0.7 , and all of a sudden we
started seeing unexpected behavior. One table got locked after we ran one
simple INSERT on one test item.
Nothing else was running against that table as far as we know, and the
query is frozen there now. After some
Hello all,
I have a setup in which four client machines access
a Postgres database (8.1.1) (on a Linux box). So,
there are connections from each machine to the
database; hence, the Linux box has about 2 postgres
processes associated with each machine.
I am using the JDBC driver
(postgresql-8.
Hi!
I have following problem:
I use php with postgres as backend. Every time, I run some queries,
postgres creates a lot of processes - this causes extremely high processor
usage.
I execute some queries in quasi-parallel way, cause I need its results.
But other are executing and every time I fre
