Re: Adding new field to big table
| От | acanada |
|---|---|
| Тема | Re: Adding new field to big table |
| Дата | |
| Msg-id | E91DB097-26CA-4B7A-B814-94EF04C5C8A5@cnio.es обсуждение исходный текст |
| Ответ на | Re: Adding new field to big table (Jeff Janes <jeff.janes@gmail.com>) |
| Ответы |
Re: Adding new field to big table
(Jeff Janes <jeff.janes@gmail.com>)
|
| Список | pgsql-performance |
On Fri, Mar 14, 2014 at 10:06 AM, acanada <acanada@cnio.es> wrote:Hello Jeff,The lock time is not a problem. The problem is that takes too much time. I will need to add more fields to this table in the near future and I'd like to know if the process can be accelerated by any parameter, workaround or whatever...Thank you for your answer.OK. Can you provide an explain (analyze, buffers), and the other information described here: http://wiki.postgresql.org/wiki/Slow_Query_QuestionsIt may be faster to make a new table by selecting a join on the existing tables and then replace the master table with it.Also, if you are going to be doing a lot of bulk updates like this, lowering the fillfactor to below 50% might be helpful.Cheers,Jeff
**NOTA DE CONFIDENCIALIDAD** Este correo electrónico, y en su caso los ficheros adjuntos, pueden contener información protegida para el uso exclusivo de su destinatario. Se prohíbe la distribución, reproducción o cualquier otro tipo de transmisión por parte de otra persona que no sea el destinatario. Si usted recibe por error este correo, se ruega comunicarlo al remitente y borrar el mensaje recibido.
**CONFIDENTIALITY NOTICE** This email communication and any attachments may contain confidential and privileged information for the sole use of the designated recipient named above. Distribution, reproduction or any other use of this transmission by any party other than the intended recipient is prohibited. If you are not the intended recipient please contact the sender and delete all copies.
В списке pgsql-performance по дате отправления: