Thanks. While creating that very file, I discovered that 1 row had blanks
in every field despite a column having a *NOT NULL* constraint and another
column being a* *serial. Removing that column appears to fixed the problem.
Something about that column made Postgres unhappy, though. If I ran these
WHERE citation_id IS NOT NULL
WHERE citation_id IS NULL
I got this result:
Not clear how adding a WHERE clause, whose only practical effect is to
reduce the number of rows returned, could cause *more* rows to be returned.
That seems buggy to me.
On Fri, Mar 16, 2012 at 12:56 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> aren(at)arencambre(dot)com writes:
> > (Note that this issue is described fully at
> > A few knowledgeable people have weighed in, and there is no solution
> > identified.)
> This might be a bug, but you've not provided sufficient information for
> someone else to reproduce the problem. What would be good is a SQL
> script that reproduces the error from a standing start (empty database).
> regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Kevin Grittner||Date: 2012-03-18 20:22:38|
|Subject: Re: BUG #6535: LEFT JOIN on large table is altering
|Previous:||From: Jaime Casanova||Date: 2012-03-18 16:11:27|
|Subject: Re: Bug in postgresql 8.1|