Postgres Pro
Downloads
Home   >   mailing lists

Re: About the performance of startup after dropping many tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: About the performance of startup after dropping many tables
Date
Msg-id 5095.1298000244@sss.pgh.pa.us
Whole thread Raw
In response to About the performance of startup after dropping many tables  (Gan Jiadong <ganjd@huawei.com>)
Responses Re: About the performance of startup after dropping many tables  (Gan Jiadong <ganjd@huawei.com>)
Re: About the performance of startup after dropping many tables  (Gan Jiadong <ganjd@huawei.com>)
Re: About the performance of startup after dropping many tables  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
Gan Jiadong <ganjd@huawei.com> writes:
> we have PG 8.3.13 in our system. When running performance cases, we find the
> startup recovery cost about 3 minutes. It is too long in our system. 

Maybe you should rethink the assumption that dropping 40000 tables is a
cheap operation.  Why do you have that many in the first place, let
alone that many that you drop and recreate frequently?  Almost
certainly, you need a better-conceived schema.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: WIP - Add ability to constrain backend temporary file space
Next
From: Tom Lane
Date:
Subject: Re: Add support for logging the current role