Jan-Peter Seifert writes:
> Tom Lane wrote:
>> I don't think there's really a problem here. You've apparently got some
>> obsolete syntax in your CREATE commands:
>>
>>> id integer NOT NULL DEFAULT nextval(('public.t2_id_seq'::text)::regclass)
> ... But then I saw the difference in nextval synt
"robert treat" writes:
> Apparently the assignment of the integer value is somehow dependent on the
> name of the out parameter; when it matches the column name, you get nulls
> back. Is this a bug?
No, it's expected behavior. You're "accumulating" n copies of the
current value of the paramete
On Tuesday 16 December 2008 15:40:17 robert treat wrote:
> The following bug has been logged online:
>
> Bug reference: 4585
> Logged by: robert treat
> Email address: xzi...@users.sourceforge.net
> PostgreSQL version: 8.3.x
> Operating system: solaris/linux
> Description:
On Tue, Dec 16, 2008 at 8:39 PM, Mark Muzenhardt
wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4584
> Logged by: Mark Muzenhardt
> Email address: mark.muzenha...@arcor.de
> PostgreSQL version: 8.3.5-2
> Operating system: Windows XP professional
> Desc
The following bug has been logged online:
Bug reference: 4584
Logged by: Mark Muzenhardt
Email address: mark.muzenha...@arcor.de
PostgreSQL version: 8.3.5-2
Operating system: Windows XP professional
Description:PostgreSQL service doesn't start
Details:
I have instal
The following bug has been logged online:
Bug reference: 4585
Logged by: robert treat
Email address: xzi...@users.sourceforge.net
PostgreSQL version: 8.3.x
Operating system: solaris/linux
Description:out parameter name cuases disruption in custom
aggregate?
Details:
Tom Lane wrote:
Thank you very much for your quick reply. I wanted to do some testing
before reporting back.
> "Jan-Peter Seifert" writes:
>> there's a problem with renaming sequences in our databases.
>
> I don't think there's really a problem here. You've apparently got some
> obsolete synta
