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

Re: WIP: default values for function parameters

From: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: default values for function parameters
Date: 2008-11-30 20:13:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
2008/11/30 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> There are two ways to fix this, both having some validity:
>> 1. We create a second version of pg_get_function_arguments() that produces
>> arguments without default values decoration.  This is probably the
>> technically sound thing to do.

I'll prepare new patch with this change.

> Yes.  I think that the argument for allowing parameter names in commands
> like ALTER FUNCTION is that the user might consider them part of the
> function's identity.  This can hardly be claimed for default values.
> Also, there's a third possibility: we could revert the decision to allow
> pg_dump to depend on pg_get_function_arguments in the first place.  That
> was really the lazy man's approach to begin with.  The more we allow
> pg_dump to depend on backend functions that work in a SnapshotNow world,
> the more risk we have of producing inconsistent dumps.

I don't understand well. Transactions is spanish village for me. So
there will be some finalizing necessary from You or Peter.

Pavel Stehule

>                        regards, tom lane

In response to

pgsql-hackers by date

Next:From: Neil ConwayDate: 2008-11-30 21:03:29
Subject: Re: pgsql: Remove inappropriate memory context switch in
Previous:From: David RowleyDate: 2008-11-30 19:11:10
Subject: Re: Windowing Function Patch Review -> Standard Conformance

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