Re: PostgreSQL 8.0.6 crash
От
Greg Stark
Тема
Re: PostgreSQL 8.0.6 crash
Дата
Msg-id
878xsk70kd.fsf@stark.xeocode.com
Ответ на
Re: PostgreSQL 8.0.6 crash (Stephen Frost)
Список
Дерево обсуждения
PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash "Jim C. Nasby" <jnasby@pervasive.com>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash "Jim C. Nasby" <jnasby@pervasive.com>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash Rick Gigger <rick@alpinenetworking.com>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash "Jim C. Nasby" <jnasby@pervasive.com>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash "Jim C. Nasby" <jnasby@pervasive.com>
Re: PostgreSQL 8.0.6 crash Stephen Frost <sfrost@snowman.net>
Re: PostgreSQL 8.0.6 crash Stephen Frost <sfrost@snowman.net>
Re: PostgreSQL 8.0.6 crash Greg Stark <gsstark@mit.edu>
Re: PostgreSQL 8.0.6 crash Alvaro Herrera <alvherre@commandprompt.com>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash Stephen Frost <sfrost@snowman.net>
Re: PostgreSQL 8.0.6 crash Greg Stark <gsstark@mit.edu>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash "Jim C. Nasby" <jnasby@pervasive.com>
Re: PostgreSQL 8.0.6 crash Martijn van Oosterhout <kleptog@svana.org>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Re: PostgreSQL 8.0.6 crash Ernst Herzberg <earny@net4u.de>
Re: PostgreSQL 8.0.6 crash "Jim C. Nasby" <jnasby@pervasive.com>
Re: PostgreSQL 8.0.6 crash Martijn van Oosterhout <kleptog@svana.org>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash Greg Stark <gsstark@mit.edu>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash Greg Stark <gsstark@mit.edu>
Re: PostgreSQL 8.0.6 crash Bruce Momjian <pgman@candle.pha.pa.us>
Re: PostgreSQL 8.0.6 crash Tom Lane <tgl@sss.pgh.pa.us>
Re: PostgreSQL 8.0.6 crash Rick Gigger <rick@alpinenetworking.com>
Re: PostgreSQL 8.0.6 crash Andrew Dunstan <andrew@dunslane.net>
Re: PostgreSQL 8.0.6 crash "Mark Woodward" <pgsql@mohawksoft.com>
Stephen Frost writes: > * Tom Lane (tgl@sss.pgh.pa.us) wrote: > > Greg Stark writes: > > > It doesn't seem like a bad idea to have a max_memory parameter that if a > > > backend ever exceeded it would immediately abort the current > > > transaction. > > > > See ulimit (or local equivalent). > > As much as setting ulimit in shell scripts is fun, I have to admit that > I really don't see it happening very much. For one thing it requires admin access to the startup scripts to arrange this. And it's always cluster-wide. Having a GUC parameter would mean it could be set per-session. Even if the GUC parameter were just implemented by calling setrlimit it might be useful. -- greg
В списке pgsql-hackers по дате отправления