See below:
On Wed, Mar 10, 2010 at 9:28 PM, Paul McGarry wrote:
> Hi there,
>
> I'm after a little bit of advice on the shared_buffers setting (I have
> read the various docs on/linked from the performance tuning wiki page,
> some very helpful stuff there so thanks to those people).
>
> I am se
On Mon, Mar 15, 2010 at 10:53 AM, Tom Lane wrote:
> Greg Smith writes:
> > VJK wrote:
> >> Since Pg does not use the concept of rollback segments, it is unclear
> >> why deletion produces so much disk IO (4GB).
>
> For an example like this one, you have to ke
Inline:
On Mon, Mar 15, 2010 at 10:42 AM, Greg Smith wrote:
> VJK wrote:
>
>> Since Pg does not use the concept of rollback segments, it is unclear why
>> deletion produces so much disk IO (4GB).
>>
>
> With PostgreSQL's write-ahead log, MVCC and related
Inline:
On Mon, Mar 15, 2010 at 10:12 AM, Kevin Grittner <
kevin.gritt...@wicourts.gov> wrote:
> VJK wrote:
>
> > the source 1.9GB (19MB x 100) resulted in 5GB of actual disk IO
>
> > Deletion (delete from x2) took 32 seconds with 12 seconds CPU and
> > 20 sec
A quick test:
-
1. create table x1(x int, y bytea);
2. Load some data say with python:
cp /opt/java/src.zip ~/tmp/a.dat (19MB)
##
import psycopg2
conn = psycopg2.connect("dbname='test' user='*' password=''
host='127.0.0.1'");
conn.cursor().execute("INSERT INTO x1 VALUES (1, %s)",
(psyc
