Postgres Pro
Downloads
Home   >   mailing lists

Thread: row name length

row name length

From
Adam Rose
Date:
I noticed in the documentation that row length is unlimited.  I think I
took that to mean row name length is now unlimited.  But, row
name length still appears to be set to a static width.  Do I still need to
recompile postgres to get 64 character row headers?

Postgres 7.1 RPMS
Redhat 6.2


Help is always appreciated

-- 
Adam Rose

Re: row name length

From
Peter Eisentraut
Date:
Adam Rose writes:

> I noticed in the documentation that row length is unlimited.  I think I
> took that to mean row name length is now unlimited.  But, row

You took that wrong...

> name length still appears to be set to a static width.  Do I still need to
> recompile postgres to get 64 character row headers?

Yes.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter

Re: row name length

From
Adam Rose
Date:
Thanks for you help

On Mon, 23 Apr 2001, Peter Eisentraut wrote:

> Adam Rose writes:
> 
> > I noticed in the documentation that row length is unlimited.  I think I
> > took that to mean row name length is now unlimited.  But, row
> 
> You took that wrong...
> 
> > name length still appears to be set to a static width.  Do I still need to
> > recompile postgres to get 64 character row headers?
> 
> Yes.
> 
> 

-- 
Adam Rose

Re: row name length

From
Adam Rose
Date:
Just a question, where is NAMEDATALEN now in 7.1, I didn't see it in
postgres.h.  If this is no longer used to change column name length, what
is? Your help is appreciated.

- 
Adam Rose

ERROR: parser: parse error at or near "JOIN"

From
Fernando Nasser
Date:
Is anyone else seeing this?

I have the current CVS sources and "make check" ends up with one
failure.  My regression.diffs shows:


*** ./expected/join.out Thu Dec 14 17:30:45 2000
--- ./results/join.out  Mon Apr 23 20:23:15 2001
***************
*** 1845,1851 **** -- UNION JOIN isn't implemented yet SELECT '' AS "xxx", *   FROM J1_TBL UNION JOIN J2_TBL;
! ERROR:  UNION JOIN is not implemented yet -- -- Clean up --
--- 1845,1851 ---- -- UNION JOIN isn't implemented yet SELECT '' AS "xxx", *   FROM J1_TBL UNION JOIN J2_TBL;
! ERROR:  parser: parse error at or near "JOIN" -- -- Clean up --

======================================================================


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

Re: ERROR: parser: parse error at or near "JOIN"

From
Fernando Nasser
Date:
Please disregard this.  This message was held by Majordomo for a couple
of days and I have already resent it.

Tom Lane has already solved my problem (I had a miscompiled version of
bison in my machine).

Regards to all,
Fernando


Fernando Nasser wrote:
> 
> Is anyone else seeing this?
> 
> I have the current CVS sources and "make check" ends up with one
> failure.  My regression.diffs shows:
> 
> *** ./expected/join.out Thu Dec 14 17:30:45 2000
> --- ./results/join.out  Mon Apr 23 20:23:15 2001
> ***************
> *** 1845,1851 ****
>   -- UNION JOIN isn't implemented yet
>   SELECT '' AS "xxx", *
>     FROM J1_TBL UNION JOIN J2_TBL;
> ! ERROR:  UNION JOIN is not implemented yet
>   --
>   -- Clean up
>   --
> --- 1845,1851 ----
>   -- UNION JOIN isn't implemented yet
>   SELECT '' AS "xxx", *
>     FROM J1_TBL UNION JOIN J2_TBL;
> ! ERROR:  parser: parse error at or near "JOIN"
>   --
>   -- Clean up
>   --
> 

-- 
Fernando Nasser
Red Hat Inc.                     E-Mail:  fnasser@redhat.com