This patch allows ALTER FUNCTION set change a function's strictness. In
and of itself this isn't very useful, but it is defined in SQL2003, so
it's probably worth implementing.
Notes:
- the optimizer considers strictness; for example, the optimizer will
pre-evaluate calls to a strict function
Resubmission of yesterday's patch so that it would
cont conflict with Bruce's cvs commit. Pleas apply.
Best regards,
Nicolai.
On Sat, 12 Mar 2005 01:58:15 +0200, Nicolai Tufar [EMAIL PROTECTED] wrote:
On Thu, 10 Mar 2005 19:21:41 -0500 (EST), Bruce Momjian
pgman@candle.pha.pa.us wrote:
The
Mark Kirkwood wrote:
A couple of minor amendments here:
- remove link to libpq (from cut+past of dblnk's Makefile)
- add comment for pg_buffercache module in contrib/README
- change my listed email to this one (I have resigned)
Applied, thanks for the patch.
BTW, I removed the REGRESS=... line
Neil Conway [EMAIL PROTECTED] writes:
This patch allows ALTER FUNCTION set change a function's strictness. In
and of itself this isn't very useful, but it is defined in SQL2003, so
it's probably worth implementing.
You realize of course that that can already be done with CREATE OR
REPLACE
On Sat, Mar 12, 2005 at 05:59:24PM +1100, Neil Conway wrote:
Marko Kreen wrote:
Please apply this also to stable branches (8.0 / 7.4).
Should it be backpatched to 7.3 and 7.2 as well?
It would be nice. I didn't know there are releases of those
planned as well.
Now looking into it, 7.3 and
Neil Conway wrote:
Bruce Momjian wrote:
Handle carriage returns and line feeds in COPY CSV mode.
Would it be possible to have some regression tests for this?
will this do?
cheers
andrew
Index: src/test/regress/input/copy.source
Well, I was really hoping something would end up in the log file.
The situation is that our clients - sometimes not that computer
savvy - go perhaps a year without us being involved (unless
the log monitoring scripts show something abnormal; or if the
system breaks).
The primary motivation for
Ron Mayer wrote:
Well, I was really hoping something would end up in the log file.
The situation is that our clients - sometimes not that computer
savvy - go perhaps a year without us being involved (unless
the log monitoring scripts show something abnormal; or if the
system breaks).
The