Skip site navigation (1) Skip section navigation (2)

Re: COPY FROM command v8.1.4

From: Ray Stell <stellr(at)cns(dot)vt(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: theman <bitsandbytes88(at)hotmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: COPY FROM command v8.1.4
Date: 2006-09-23 17:20:59
Message-ID: 20060923172059.GB4831@cns.vt.edu (view raw or flat)
Thread:
Lists: pgsql-admin
Curious how you get to an OS kernel bug from these writes?  Aren't we
missing the associated db reads in this trc data?  Maybe there been
other data provided off the list?  Would love to see it.

Thanks.



On Fri, Sep 22, 2006 at 05:59:31PM -0400, Tom Lane wrote:
> "theman" <bitsandbytes88(at)hotmail(dot)com> writes:
> > lseek(10, 0, SEEK_END)                  = 913072128
> > write(10, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192
> > lseek(10, 0, SEEK_END)                  = 913080320
> > write(10, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192
> > lseek(10, 0, SEEK_END)                  = 913088512
> > write(10, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192
> > lseek(10, 0, SEEK_END)                  = 913088512
> > write(10, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192
> > lseek(10, 0, SEEK_END)                  = 913096704
> > write(10, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192
> 
> Boy, that looks like a smoking gun to me.  We're dealing with a kernel
> bug.
> 
> What's the platform here, including the exact kernel version?  What
> filesystem are you storing the database on?
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2006-09-23 17:41:00
Subject: Re: COPY FROM command v8.1.4
Previous:From: Chris BrowneDate: 2006-09-22 22:46:32
Subject: Re: Security Concerns over User 'postgres'

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group