I am consistently getting "Server process exited with status 139" whilst
trying to create a straightforward index - "Create index test1 on
voter(name);"
The table has 13 million records, and the longest name in the VARCHAR field
being indexed is 47 characters.
My system:
ABIT BP6, 2 x Cel
>> Try it with the beta version's ODBC driver ...
> How do I get it? I looked through the Development
> version FTP filetree, and can't find the ODBC driver
> anywhere. Link ... pretty please?
Darn if I know, I don't do Windows. Dave Page might have
a precompiled .dll available.
> It appears that the triggers were never updated to now refer to 'old'
> instead of to current_usage when it was renamed, but were still
> associated with 'old' for purposes of dropping them. (i presume this
> is because the triggers were attached to 'old' by oid, which didnt
> change when it wa
[EMAIL PROTECTED] writes:
> delete something that referential triggers from tran 1 just checked and are relying
>on.
> commit
> tran 2 triggers see pre-tran 1 data and think its ok to delete.
> tran 2 finishes before tran 1.
> tran 1 already checked that tran 2 row and thinks its fine, commit
> f
[EMAIL PROTECTED] writes:
> Windows 98 O.E.
> MS Access 97 SR 2a
> MDAC 2.5 and DCOM 98
> Postgres ODBC 6.50.00
^
> on two workstations.
> Postgres ODBC, whcih workes fine when the Postgres server runs 7.0.3,
> does not work when the server runs 7.1 beta 3.
Try it with the
Dave E Martin ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
bug #126, referential integrity makes big LOCK
Long Description
In referral to bug #126, where someone is wondering why triggers use FOR UPDATE on
data they aren't
[EMAIL PROTECTED] writes:
> The documentation in both 7.1 and 7.0.3 talks about the bool type but
> both fail to actually mention the name(s) of the type in the section
> on booleans.
>
> presumably its called 'boolean' based on the description, but it could
> be clearer. one has to refer to tabl
Dave E Martin ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
alter table rename and ruminations on referential integrity
Long Description
PostgreSQL 7.0.3 on i686-pc-linux-gnu, compiled by gcc 2.95.2
I suspect symptoms of thi
Dave E Martin ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
bool type could be better documented
Long Description
The documentation in both 7.1 and 7.0.3 talks about the bool type but both fail to
actually mention the name(s
Josh Berkus ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
PgSQL 7.1 beta 3 breaks ODBC
Long Description
I'm running:
Postgres 7.1 beta 3 on SuSE Linux 7.0
on the server, and
Windows 98 O.E.
MS Access 97 SR 2a
MDAC 2.5 and DC
[EMAIL PROTECTED] writes:
> I am consistently getting "Server process exited with status 139"
> whilst trying to create a straightforward index - "Create index test1
> on voter(name);"
Hm. I wonder if the table contains any corrupted data. If you do
something else that scans all the name entrie
Jeremy Young ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Server process exited with status 139
Long Description
(I have also emailed [EMAIL PROTECTED] - not sure if that will get through!)
I am consistently getting "Server
12 matches
Mail list logo
