Thread

1. vlen in libpq using user defined data type

   David Hartwig <daveh@insightdist.com> — 1998-09-09T20:55:22Z

   I have come across a situation with 6.4 which has rendered at least some
   of my home made data types unusable.   Specifically, the data type,
   accntnum, is a General Ledger account number type.   (i.e.  9999-99
   format)    It is stored internally as an 4 byte integer; it is used
   externally as a string and passed by reference internally.  An IP data
   type may be handled in a similar way.     I had no problems at 6.3.2.
   
   Anyway, as pqlib reads the string sent to it by the backend (a la psql),
   it must first read the length of each string.  The problem is that the
   length of the string for accntnum in some outrageously large number
   which ultimately hangs psql.  BTW,  atttypemod = -1 and typlen = 4 in
   the FE.
   
   Did something changed in the way a string is constructed on the BE
   before sending to the FE to cause this?
   
   Have the basic semantics changed (intentionally or unintentionally) for
   the establishment of data types?
   
   Any assistance is appreciated.
   
   
   
   
   
   

2. Re: [HACKERS] vlen in libpq using user defined data type

   Bruce Momjian <maillist@candle.pha.pa.us> — 1998-09-09T21:38:36Z

   > I have come across a situation with 6.4 which has rendered at least some
   > of my home made data types unusable.   Specifically, the data type,
   > accntnum, is a General Ledger account number type.   (i.e.  9999-99
   > format)    It is stored internally as an 4 byte integer; it is used
   > externally as a string and passed by reference internally.  An IP data
   > type may be handled in a similar way.     I had no problems at 6.3.2.
   > 
   > Anyway, as pqlib reads the string sent to it by the backend (a la psql),
   > it must first read the length of each string.  The problem is that the
   > length of the string for accntnum in some outrageously large number
   > which ultimately hangs psql.  BTW,  atttypemod = -1 and typlen = 4 in
   > the FE.
   > 
   > Did something changed in the way a string is constructed on the BE
   > before sending to the FE to cause this?
   > 
   > Have the basic semantics changed (intentionally or unintentionally) for
   > the establishment of data types?
   
   Just reported today by another user.  Tom Lane is working on this.
   
   -- 
   Bruce Momjian                          |  830 Blythe Avenue
   maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
     +  If your life is a hard drive,     |  (610) 353-9879(w)
     +  Christ can be your backup.        |  (610) 853-3000(h)