| From: | Andy Colson <andy(at)squeakycode(dot)net> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Michael Andreasen <michael(at)dunlops(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Fastest pq_restore? |
| Date: | 2011-03-18 19:10:05 |
| Message-ID: | 4D83AE0D.1020607@squeakycode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 3/18/2011 9:38 AM, Kevin Grittner wrote:
> Andy Colson<andy(at)squeakycode(dot)net> wrote:
>> On 03/17/2011 09:25 AM, Michael Andreasen wrote:
>
>>> I've been looking around for information on doing a pg_restore as
>>> fast as possible.
>
>> bgwriter_lru_maxpages = 0
>
> I hadn't thought much about that last one -- do you have benchmarks
> to confirm that it helped with a bulk load?
>
Nope, I got it from the "running with scissors" thread (I think), (maybe
from Greg Smith)
or here:
http://rhaas.blogspot.com/2010/06/postgresql-as-in-memory-only-database_24.html
I dont recall exactly. I saw it, add added a comment to my .conf just
incase I ever needed it.
-Andy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-03-18 19:21:16 | Re: Help: massive parallel update to the same table |
| Previous Message | Red Maple | 2011-03-18 18:21:09 | Re: Help: massive parallel update to the same table |