Thread

1. Re: [HACKERS] How to...?

   Andrew Martin <martin@biochemistry.ucl.ac.uk> — 1998-03-09T11:04:56Z

   > 	Then, using what was left, I did:
   > 
   > psql -e < db.dump 
   > 
   > 	Again.  Failed misearbly, with the following coming from the 'copy
   > to <relname> from stdin;' section:
   > 
   > 344984  johnb   xgSldZdYEgIWo           clio.trends.ca  n       \N
   
   I got something kind-of similar with a core dump... This was 'cos of a 
   column name which is now a reserved word.
   
   
   Andrew
   
   ----------------------------------------------------------------------------
   Dr. Andrew C.R. Martin                             University College London
   EMAIL: (Work) martin@biochem.ucl.ac.uk    (Home) andrew@stagleys.demon.co.uk
   URL:   http://www.biochem.ucl.ac.uk/~martin
   Tel:   (Work) +44(0)171 419 3890                    (Home) +44(0)1372 275775
   
   

2. Re: [HACKERS] How to...?

   Marc Fournier <scrappy@hub.org> — 1998-03-09T13:04:32Z

   On Mon, 9 Mar 1998, Andrew Martin wrote:
   
   > > 	Then, using what was left, I did:
   > > 
   > > psql -e < db.dump 
   > > 
   > > 	Again.  Failed misearbly, with the following coming from the 'copy
   > > to <relname> from stdin;' section:
   > > 
   > > 344984  johnb   xgSldZdYEgIWo           clio.trends.ca  n       \N
   > 
   > I got something kind-of similar with a core dump... This was 'cos of a 
   > column name which is now a reserved word.
   
   	Ack, I fear you are correct...the third field above is 'password',
   which became a reserved word in v6.3...oh man, is this upgrade ever going
   to hurt...my 'db.dump' file is 84Meg...vi just loves it :)
   
   
   
   

3. Re: [HACKERS] How to...?

   Maarten Boekhold <maartenb@dutepp2.et.tudelft.nl> — 1998-03-09T15:47:10Z

   On Mon, 9 Mar 1998, The Hermit Hacker wrote:
   
   > On Mon, 9 Mar 1998, Andrew Martin wrote:
   > 
   > > > 	Then, using what was left, I did:
   > > > 
   > > > psql -e < db.dump 
   > > > 
   > > > 	Again.  Failed misearbly, with the following coming from the 'copy
   > > > to <relname> from stdin;' section:
   > > > 
   > > > 344984  johnb   xgSldZdYEgIWo           clio.trends.ca  n       \N
   > > 
   > > I got something kind-of similar with a core dump... This was 'cos of a 
   > > column name which is now a reserved word.
   > 
   > 	Ack, I fear you are correct...the third field above is 'password',
   > which became a reserved word in v6.3...oh man, is this upgrade ever going
   > to hurt...my 'db.dump' file is 84Meg...vi just loves it :)
   
   How about starting up your old pgsql, then psql, the 'alter table rename 
   column.....'
   
   Maarten
   
   _____________________________________________________________________________
   | TU Delft, The Netherlands, Faculty of Information Technology and Systems  |
   |                   Department of Electrical Engineering                    |
   |           Computer Architecture and Digital Technique section             |
   |                          M.Boekhold@et.tudelft.nl                         |
   -----------------------------------------------------------------------------
   
   
   

4. Re: [HACKERS] How to...?

   Marc Fournier <scrappy@hub.org> — 1998-03-09T16:52:28Z

   On Mon, 9 Mar 1998, Maarten Boekhold wrote:
   
   > On Mon, 9 Mar 1998, The Hermit Hacker wrote:
   > 
   > > On Mon, 9 Mar 1998, Andrew Martin wrote:
   > > 
   > > > > 	Then, using what was left, I did:
   > > > > 
   > > > > psql -e < db.dump 
   > > > > 
   > > > > 	Again.  Failed misearbly, with the following coming from the 'copy
   > > > > to <relname> from stdin;' section:
   > > > > 
   > > > > 344984  johnb   xgSldZdYEgIWo           clio.trends.ca  n       \N
   > > > 
   > > > I got something kind-of similar with a core dump... This was 'cos of a 
   > > > column name which is now a reserved word.
   > > 
   > > 	Ack, I fear you are correct...the third field above is 'password',
   > > which became a reserved word in v6.3...oh man, is this upgrade ever going
   > > to hurt...my 'db.dump' file is 84Meg...vi just loves it :)
   > 
   > How about starting up your old pgsql, then psql, the 'alter table rename 
   > column.....'
   
   	Cause I keep forgetting that I can do that :(  Point taken and
   will try that out, thanks...
   
   
   
   

5. Re: [HACKERS] How to...?

   Bruce Momjian <maillist@candle.pha.pa.us> — 1998-03-09T17:11:37Z

   > > 	Ack, I fear you are correct...the third field above is 'password',
   > > which became a reserved word in v6.3...oh man, is this upgrade ever going
   > > to hurt...my 'db.dump' file is 84Meg...vi just loves it :)
   > 
   > How about starting up your old pgsql, then psql, the 'alter table rename 
   > column.....'
   
   I assume normal users do the pg_dump, delete their databases and old
   binaries, then try to reload into 6.3.
   
   -- 
   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)
   
   

6. Re: [HACKERS] How to...?

   Thomas Lockhart <lockhart@alumni.caltech.edu> — 1998-03-10T04:00:42Z

   >         Ack, I fear you are correct...the third field above is 'password',
   > which became a reserved word in v6.3...oh man, is this upgrade ever going
   > to hurt...my 'db.dump' file is 84Meg...vi just loves it :)
   
   Well, this doesn't solve the general problem, but "password" can be used as a
   column name without inducing shift/reduce conflicts. I'll patch the source
   tree sometime soon; in the meantime add the obvious source around line 4618
   in gram.y:
   
     | PASSWORD { $$ = "password"; }
   
   (add tabs to taste :)
   
                                          - Tom