Hi All,

My problems seem to be getting worse!!

Yesterday I was only getting a crash when I tried to create a table.

Today, with the latest from cvs I'm getting a crash on a simple select.

Here's the backtrace:-

Program received signal SIGSEGV, Segmentation fault.
0x95564 in transformTargetList (pstate=0x15c790, targetlist=0x15ec10)
    at parse_target.c:583
583                                             attrname = 
strVal(lfirst(att->attrs));
(gdb) bt
#0  0x95564 in transformTargetList (pstate=0x15c790, targetlist=0x15ec10)
    at parse_target.c:583
#1  0x885f4 in transformSelectStmt (pstate=0x15c790, stmt=0x15c7d0) at 
analyze.c:867
#2  0x877a8 in transformStmt (pstate=0x15c790, parseTree=0x15c7d0) at 
analyze.c:190
#3  0x87504 in parse_analyze (pl=0x15eb50, parentParseState=0x0) at analyze.c:76
#4  0x8e8fc in parser (str=0x0, typev=0x0, nargs=0) at parser.c:64
#5  0xaef60 in pg_parse_and_plan (
    query_string=0xefffd1a0 " select * from pg_class;", typev=0x0, nargs=0,
    queryListP=0xefffd0bc, dest=Remote, aclOverride=0 '\000') at postgres.c:402
#6  0xaf420 in pg_exec_query_dest (
    query_string=0xefffd1a0 " select * from pg_class;", dest=Remote,
    aclOverride=0 '\000') at postgres.c:668
#7  0xaf3d4 in pg_exec_query (query_string=0xefffd1a0 " select * from 
pg_class;")
    at postgres.c:643
#8  0xb0388 in PostgresMain (argc=1169408, argv=0xeffff1a0, real_argc=10,
    real_argv=0xeffffd84) at postgres.c:1480
#9  0x98f7c in DoBackend (port=0xff400) at postmaster.c:1412
#10 0x989b8 in BackendStartup (port=0x15fc00) at postmaster.c:1191
#11 0x97fe4 in ServerLoop () at postmaster.c:725
#12 0x97b3c in PostmasterMain (argc=0, argv=0xeffffd84) at postmaster.c:534
#13 0x6c30c in main (argc=10, argv=0xeffffd84) at main.c:93

For info, each time I do a cvs update and then copy the entire tree to
another machine. The target directory on the other machine is an empty
/usr/local/pgsql.

I then do a configure/make/make install/initdb before commencing
any testing.

I'm starting to get worried about my hardware/OS as no-one else
seems to be reporting similar problems.

For reference.

SPARC/Linux (Redhat 4.2) running on a SPARCstation IPC.

Is anyone else trying to build the latest source on any SPARC
hardware with any OS? (Solaris,SunOS)

Keith.

Bruce Momjian <maillist@candle.pha.pa.us>
> 
> Seems like there is some problem with cvs and people seeing all my
> changes, causing initdb problems.
> 
> The only solution that has worked for two people is to re-download the
> entire cvs tree.


Tue, 25 Aug 1998 22:10:46 +0100 (BST)
Keith Parks <emkxp01@mtcc.demon.co.uk>
Re: [HACKERS] initdb problems
I am applying a patch now.  I also got your message about the
alignments.  They should be 'd' as you said.  Seems like the bootstrap
has it wrong, as it defaults to 'i' for things it could not figure out. 
Didn't matter before, but multi-key indexes require them to be correct. 
Should have something tomorrow.


> Hi All,
> 
> My problems seem to be getting worse!!
> 
> Yesterday I was only getting a crash when I tried to create a table.
> 
> Today, with the latest from cvs I'm getting a crash on a simple select.
> 
> Here's the backtrace:-
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x95564 in transformTargetList (pstate=0x15c790, targetlist=0x15ec10)
>     at parse_target.c:583
> 583                                             attrname = 
> strVal(lfirst(att->attrs));
> (gdb) bt
> #0  0x95564 in transformTargetList (pstate=0x15c790, targetlist=0x15ec10)
>     at parse_target.c:583
> #1  0x885f4 in transformSelectStmt (pstate=0x15c790, stmt=0x15c7d0) at 
> analyze.c:867
> #2  0x877a8 in transformStmt (pstate=0x15c790, parseTree=0x15c7d0) at 
> analyze.c:190
> #3  0x87504 in parse_analyze (pl=0x15eb50, parentParseState=0x0) at analyze.c:76
> #4  0x8e8fc in parser (str=0x0, typev=0x0, nargs=0) at parser.c:64
> #5  0xaef60 in pg_parse_and_plan (
>     query_string=0xefffd1a0 " select * from pg_class;", typev=0x0, nargs=0,
>     queryListP=0xefffd0bc, dest=Remote, aclOverride=0 '\000') at postgres.c:402
> #6  0xaf420 in pg_exec_query_dest (
>     query_string=0xefffd1a0 " select * from pg_class;", dest=Remote,
>     aclOverride=0 '\000') at postgres.c:668
> #7  0xaf3d4 in pg_exec_query (query_string=0xefffd1a0 " select * from 
> pg_class;")
>     at postgres.c:643
> #8  0xb0388 in PostgresMain (argc=1169408, argv=0xeffff1a0, real_argc=10,
>     real_argv=0xeffffd84) at postgres.c:1480
> #9  0x98f7c in DoBackend (port=0xff400) at postmaster.c:1412
> #10 0x989b8 in BackendStartup (port=0x15fc00) at postmaster.c:1191
> #11 0x97fe4 in ServerLoop () at postmaster.c:725
> #12 0x97b3c in PostmasterMain (argc=0, argv=0xeffffd84) at postmaster.c:534
> #13 0x6c30c in main (argc=10, argv=0xeffffd84) at main.c:93
> 
> For info, each time I do a cvs update and then copy the entire tree to
> another machine. The target directory on the other machine is an empty
> /usr/local/pgsql.
> 
> I then do a configure/make/make install/initdb before commencing
> any testing.
> 
> I'm starting to get worried about my hardware/OS as no-one else
> seems to be reporting similar problems.
> 
> For reference.
> 
> SPARC/Linux (Redhat 4.2) running on a SPARCstation IPC.
> 
> Is anyone else trying to build the latest source on any SPARC
> hardware with any OS? (Solaris,SunOS)
> 
> Keith.
> 
> Bruce Momjian <maillist@candle.pha.pa.us>
> > 
> > Seems like there is some problem with cvs and people seeing all my
> > changes, causing initdb problems.
> > 
> > The only solution that has worked for two people is to re-download the
> > entire cvs tree.
> 
> 


-- 
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)

Tue, 25 Aug 1998 23:17:39 -0400 (EDT)
Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] initdb problems
> Hi All,
> 
> My problems seem to be getting worse!!
> 
> Yesterday I was only getting a crash when I tried to create a table.
> 
> Today, with the latest from cvs I'm getting a crash on a simple select.
> 
> Here's the backtrace:-

OK, selects should be fixed now.  Also:

select relname, attname,attalign from pg_class, pg_attribute, pg_type 
where atttypid = pg_type.oid and typname = 'name' and pg_class.oid =
attrelid and attalign != 'd'

now returns no rows, as it should.  Some tricky work, but they are all
correct now.  Let's see if that fixes the Sparc problem.

-- 
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)

Wed, 26 Aug 1998 00:52:39 -0400 (EDT)
Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] initdb problems