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

Re: bug in PG_VERSION_NUM patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: bug in PG_VERSION_NUM patch
Date: 2006-02-28 22:29:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> OK, I reread the manual page:

>        As  each input record is read, gawk splits the record into
>        fields, using the value of the FS variable  as  the  field
>        separator.   If FS is a single character, fields are sepa-
>        rated by that character.  If FS is the null  string,  then
>        each  individual character becomes a separate field.  Oth-
>        erwise, FS is expected to be a  full  regular  expression.

Hpmh.  The HPUX man page for plain awk says

          -F fs          Specify regular expression used to separate
                         fields.  The default is to recognize space and tab
                         characters, and to discard leading spaces and
                         tabs.  If the -F option is used, leading input
                         field separators are no longer discarded.

which makes me think we are treading on mighty thin ice here --- there
are lots of different versions of awk around, and some of them are
probably going to treat -F '.' as a regexp.

I'd suggest splitting the input with something more standardized.

sed 's/\./ /g' | $AWK '{printf ...

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-02-28 22:33:45
Subject: Re: bug in PG_VERSION_NUM patch
Previous:From: Hannu KrosingDate: 2006-02-28 22:10:52
Subject: Re: Automatic free space map filling

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