Re: BUG #5748: Invalid oidvector data during binary recv

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5748: Invalid oidvector data during binary recv
Date: 2010-11-11 16:17:35
Message-ID: 15909.1289492255@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

BTW ... it strikes me there's another inconsistency between oidvectorin
and oidvectorrecv, namely that the former enforces a maximum of
FUNC_MAX_ARGS elements whereas the latter has no such limit. Should we
do something about that, and if so what? It wouldn't be too hard to get
rid of the former's maximum, but I'm worried about whether any code is
dependent on an assumption that oidvectors can't get toasted. The
type's marked untoastable in pg_type, so maybe enforcing the same limit
in the latter is a safer idea.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2010-11-11 16:20:20 Re: Recovery bug
Previous Message Heikki Linnakangas 2010-11-11 16:14:33 Re: BUG #5748: Invalid oidvector data during binary recv