Re: Strangeness/bug when working with my own datatype in P ostgreSQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Солодовников Константин <ks(at)tcnet(dot)ru>
Cc: "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Strangeness/bug when working with my own datatype in P ostgreSQL
Date: 2001-02-26 15:37:04
Message-ID: 26199.983201824@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?KOI8-R?Q?=F3=CF=CC=CF=C4=CF=D7=CE=C9=CB=CF=D7_=EB=CF=CE=D3=D4=C1?= =?KOI8-R?Q?=CE=D4=C9=CE?= <ks(at)tcnet(dot)ru> writes:
> create type int1 ( input = int1_in, output = int1_out, internallength = 1,
> externallength = 3, default = "" );

I'm not sure what it will do to specify a default value for a type that
is not a legal value of the datatype --- but it can't be good. Take out
the default clause.

It also seems a tad bizarre to be treating int1 as a pass-by-reference
datatype, but that's probably not causing any misbehavior, just
inefficiency...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Vadim I. Passynkov 2001-02-26 17:25:03 pg_dump Segmentation fault(core dumped)
Previous Message Jaume Teixi 2001-02-26 14:28:47 COPY doesn't works with es_ES characters