I have 2, closely related:
1) if I have multiple pids running queries, say all selects, I have no
idea which pid is running which query
and that ties to:
2) If I try to kill 1 postgres pid (e.g. to abort a bad query), the
whole backend shuts down and rolls back.
Can we get a way to look at and then kill a specific bad query?
Maybe this is not missing functionality, it can do it and I just don't
know how. Anybody want to wisen me up? :)
Associate Director Software Development and Deployment
Great Gulf Homes / Ashton Woods Homes
Fax: (416) 441-9085
Gregory Stark wrote:
> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> FOSDEM 2009 this year. I have a pretty good idea what some them are of course,
> but I would be interested to hear if people have any complaints from personal
> experience. What would be most interesting is if you can explain an example of
> when the problem caused real inconvenience to you, since sometimes it's hard
> to see from a theoretical description where the real harm lies.
> So, what do people say? Is Postgres perfect in your world or does it do some
> things which rub you the wrong way?
> Feel free to respond on-list or if you prefer in personal emails. I do intend
> to use the ideas you give in my presentation so mark anything you wouldn't be
> happy to see in a slide at a conference some day.
In response to
pgsql-general by date
|Next:||From: Bill Moran||Date: 2009-01-29 16:44:12|
|Subject: Re: Pet Peeves?|
|Previous:||From: Gerhard Wiesinger||Date: 2009-01-29 16:31:07|
|Subject: Full backup - pg_dumpall sufficient?|