Re: pgAdmin problem - invalid page fault when migrating

From: <davidb(at)vectormath(dot)com>
To: <chriswood(at)wvda(dot)com>, <pgsql-novice(at)postgresql(dot)org>
Subject: Re: pgAdmin problem - invalid page fault when migrating
Date: 2000-07-17 15:23:28
Message-ID: 002701bff002$fbac5800$0602010a@bullwinkle.vectormath
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

In case you don't get any higher quality help...

I don't know how you are attempting to effect this
migration. Assuming you are using something which
generates scripts from your Access database to be
run in your postgres database, what you ought to
do is edit those scripts to remove the extra
quotation marks. You only ought to have quotation
marks around table names and column names (and you
only need those since you evidently are including
spaces in those names).

David Boerwinkle

-----Original Message-----
From: chriswood(at)wvda(dot)com <chriswood(at)wvda(dot)com>
To: pgsql-novice(at)postgresql(dot)org
<pgsql-novice(at)postgresql(dot)org>
Date: Monday, July 17, 2000 8:10 AM
Subject: [NOVICE] pgAdmin problem - invalid page
fault when migrating

It happens when I try to migrate an Access97 table
with 3000 rows
and 10 to 20 columns. Unfortunately, I can't save
the logfile
because the program has crashed. I did, however,
manage to take
a screenshot and type the last bit of the logfile
out (ie what was
happening when this crashed, munged a bit to take
the (likely)
confidential table name out):

Creating table: (table name)
CREATE TABLE "(table name)" ("2000 CONTACT
oat8",
"LOW#2" "float8", "YEAR EST" "text", "DESCRIPTION
OF BUS"
"text", "

So apparently it's failing on the name of a column
header, if I read
this right. Could this be caused by:

...format problems in the Access97 database?
...insufficient resources? I'm running pgAdmin on
a Celeron 366
with 64 MB RAM.
...huge table?
...network glitch?

Help is, of course, appreciated. This one has me
beat, and I'm
reasonably certain that it's not an "idiot
mistake" like my last one.

I have downloaded and installed the latest
versions of the packages
named on the pgAdmin homepage.

Here's the error Windows spat out, in case you
were wondering:

PGADMIN caused an invalid page fault in
module <unknown> at 0000:2f544355.
Registers:
EAX=00000000 CS=015f EIP=2f544355 EFLGS=00010206
EBX=00000000 SS=0167 ESP=0081c860 EBP=034bf737
ECX=00000002 DS=0167 ESI=034bf0c0 FS=121f
EDX=00000001 ES=0167 EDI=034bf739 GS=0000
Bytes at CS:EIP:

Stack dump:
56524553 22454349 65742220 2c227478 4f442220
5453454d
4d204349 2253544b 65742220 2c227478 53492220
3039204f
20223030 6f6f6222 202c226c 50584522

--------------------------------------
Christopher Wood
chriswood(at)wvda(dot)com
Community Access Technical Coordinator

http://www.wvda.com/index.html
http://www.wvcn.ns.ca/index.html
http://www.wvcn.ns.ca/~bcap/index.html
--------------------------------------

Browse pgsql-novice by date

  From Date Subject
Next Message Warren Odom 2000-07-18 13:47:41 How to get ODBC going?
Previous Message chriswood 2000-07-17 13:03:22 pgAdmin problem - invalid page fault when migrating