From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Markus Wanner <markus(at)bluegap(dot)ch> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: changing MyDatabaseId |
Date: | 2010-11-17 12:27:06 |
Message-ID: | 1289996664-sup-4015@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Markus Wanner's message of mié nov 17 07:04:04 -0300 2010:
> > Thoughts?
>
> The question obviously is whether or not this is faster than just
> terminating one backend and starting a new one. Which basically costs an
> additional termination and re-creation of a process (i.e. fork())
> AFAICS. Or what other savings do you envision?
I don't think it's a speed thing only. It would be a great thing to
have in autovacuum, for example, where we have constant problem reports
because the system failed to fork a new backend. If we could simply
reuse an already existing one, it would be a lot more robust.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Wanner | 2010-11-17 12:57:18 | Re: changing MyDatabaseId |
Previous Message | Itagaki Takahiro | 2010-11-17 11:33:55 | Overlap operators for ARRAY and NULLs |