The following bug has been logged online:
Bug reference: 5549
Logged by: David Schmitt
Email address: da...@dasz.at
PostgreSQL version: 8 and 9
Operating system: n/a
Description:Feature: plpgsql should allow DECLARE cursor FOR EXECUTE
'...'
Details:
T
On 7/9/2010 4:53 PM, Tom Lane wrote:
"David Schmitt" writes:
This is not implemented:
DECLARE
working_cursor NO SCROLL CURSOR FOR EXECUTE $$SELECT something $$ || tbl
|| $$ ... $$;
What's wrong with OPEN FOR EXECUTE?
The proposed addition seems a bit weird anyway si
The following bug has been logged online:
Bug reference: 5673
Logged by: David Schmitt
Email address: da...@dasz.at
PostgreSQL version: 8.4.4
Operating system: Windows 7
Description:Optimizer creates strange execution plan leading to
wrong results
Details
On 9/23/2010 5:33 PM, Tom Lane wrote:
"David Schmitt" writes:
Description:Optimizer creates strange execution plan leading to
wrong results
Please supply a self-contained example demonstrating the incorrect results.
The information you've provided is completely
On 9/23/2010 9:53 PM, Tom Lane wrote:
David Schmitt writes:
Executing the attached example.sql on a fresh database demonstrates the
problem I'm seeing:
Found it. If you need a patch right away, it's a one-liner:
diff --git a/src/backend/optimizer/path/allpaths.c
b/src/backend
The following bug has been logged online:
Bug reference: 5869
Logged by: David Schmitt
Email address: da...@dasz.at
PostgreSQL version: 8.4.5
Operating system: Windows 7
Description:postgresql corrupts unquoted non-ascii chars in column
aliases
Details:
Example
On 03.03.2011 16:08, Robert Haas wrote:
On Tue, Feb 8, 2011 at 2:19 AM, David Schmitt wrote:
Example query:
SELECT column as zurück FROM table;
results in corruption of the "ü" (umlaut u). This causes Npgsql to fail to
match up the columns in the result set (see
http://pgf
