From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Veikko Mäkinen <veikko(dot)makinen(at)ecom(dot)fi> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: How does the transaction buffer work? |
Date: | 2005-06-16 21:53:36 |
Message-ID: | 200506161453.37194.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Veikko,
> One way of doing this that I thought of was start a
> transaction, delete everything and then just dump new data in (copy
> perhaps). The old data would be usable to other transactions until I
> commit my insert. This would be the fastest way, but how much memory
> would this use?
Starting a transaction doesn't use any more memory than without one.
Unlike Some Other Databases, PostgreSQL's transactions occur in WAL and on
data pages, not in RAM.
> Will this cause performance issues on a heavily loaded
> server with too little memory even to begin with :)
Quite possibly, but the visibility issue won't be the problem.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Todd Landfried | 2005-06-17 02:15:08 | Re: Needed: Simplified guide to optimal memory |
Previous Message | Justin Davis | 2005-06-16 20:53:44 | could not send data to client: |