Pass collation to makeConst() instead of looking it up internally.
In nearly all cases, the caller already knows the correct collation, and
in a number of places, the value the caller has handy is more correct than
the default for the type would be. (In particular, this patch makes it
significant
Fix failure to propagate collation in negate_clause().
Turns out it was this, and not so much plpgsql, that was at fault in Stefan
Huehner's collation-error-in-a-trigger bug report of a couple weeks ago.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/c8e993503d0f1a0
Document collation handling in SQL and plpgsql functions.
This is pretty minimal but covers the bare facts.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/9b19c12e1d930a237817dd432100388990ec082a
Modified Files
--
doc/src/sgml/charset.sgml |2 +
doc/
Fix collation handling in plpgsql functions.
Make plpgsql treat the input collation as a polymorphism variable, so
that we cache separate plans for each input collation that's used in a
particular session, as per recent discussion. Propagate the input
collation to all collatable input parameters.
On Fri, Mar 25, 2011 at 08:48:42AM -0700, David Fetter wrote:
> Does this need a back-patch?
"Need" I don't know, but it's of course straight forward.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|P
Log Message:
---
renamed libpqtypes to libpqtypes.esilo.com
Modified Files:
--
libpqtypes:
groff2html (r1.10 -> r1.11)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/libpqtypes/libpqtypes/groff2html?r1=1.10&r2=1.11)
--
Sent via pgsql-committers mailing list
Remove alpha release notes.
Temporarily move some of the alpha release note disclaimers into the regular
release notes, for the sake of alpha5.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f6f0916dbdf9f2dc6bcdc550d8b3843739cdc304
Modified Files
--
doc
On Fri, Mar 25, 2011 at 02:02:16AM +, Michael Meskes wrote:
> Documented some ecpg command line options that were missing:
>
> -r no_indicator
> -r prepare
> -r questionsmarks
Does this need a back-patch?
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfette
Make walreceiver send a reply after receiving data but before flushing it.
It originally worked this way, but was changed by commit
a8a8a3e0965201df88bdfdff08f50e5c06c552b7, since which time it's been impossible
for walreceiver to ever send a reply with write_location and flush_location
set to dif
Fix broken markup, and remove tabs
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/01dd34d55ad53117c2d756da7f65b6fa07a303aa
Modified Files
--
doc/src/sgml/ref/ecpg-ref.sgml | 49 +--
1 files changed, 26 insertions(+),
10 matches
Mail list logo