Re: [ADMIN] vacuum, blownawayrealtion buffers and stale locks!

1999-06-30 Thread Bruce Momjian
> > > Shouldn't vacuum analyze be ran when the indices are in place? I think the > > > indices tell vacuum analyze which fields are important for stats gathering? > > > > > > > stats are gathered on all fields. > > Bruce, > > Forgive the naive question but I just had to do a dump, table drop a

[ADMIN] vacuum, blownawayrealtion buffers and stale locks!

1999-06-30 Thread Thomas Good
> > Shouldn't vacuum analyze be ran when the indices are in place? I think the > > indices tell vacuum analyze which fields are important for stats gathering? > > > > stats are gathered on all fields. Bruce, Forgive the naive question but I just had to do a dump, table drop and re-create and t

Re: [ADMIN] RE: [SQL] float4

1999-06-30 Thread Bruce Momjian
> ahh, so 6.5 has an answer! for our "cash and accounts payable" database i > converted the float4 field to int4, and altered the input mask on the front > end to show a decimal point, but not save it with the data. so now i am > saving $35.99 as 3599. i had to alter all reports to divide by

Re: [ADMIN] Re: vacum, locks, indicies and whatnot

1999-06-30 Thread Bruce Momjian
> At 19:52 +0300 on 29/06/1999, Mark Dalphin wrote: > > > > ... a program called AutoVac which loops over all the databases controlled by > > Postgresql, drops each index, VACUUM ANALYZE each table and then re-creates > > the index. An interesting mixture of shell, Perl and psql (no complaint, >

[ADMIN] Createuser problems

1999-06-30 Thread Paul Dlug
Whenever I run createuser I get ERROR: pg_user: Table does not exist, I don't know what to do at this point, I have setup other PostgreSQL servers with no problem, however this one is giving this error and I don't know how to fix it. Any help would be greatly appreciated, thanks in advance. --Pau

[ADMIN] upgraded to 6.4.2 and getting core dumps entering psql - help!

1999-06-30 Thread Michael Olivier
Hi folks, I've upgrading from 6.3.2 to 6.4.2 (the -3.i386.rpm version) since there aren't RPM's yet for -data and -devel pieces of 6.5 ... and am getting core dumps in 'psql' just after it starts up. As per the admin documentation, I run 'postmaster -i' as postgres user in one shell. In another

Re: [ADMIN] Transferring data to/from Paradox 4.5

1999-06-30 Thread Nikolay Mijaylov
Ok If u works with Px 4 then u probably works with Delphi too? Delphi and C++ Builder have a tool 'datapump', it can transfere entire tables or databases between any ODBC systems. (of course sometimes it make big mistakes:) Niki w3.nsi.bg/linux - Original Message - From: Jas

[ADMIN] Transferring data to/from Paradox 4.5

1999-06-30 Thread Jason Earl
I was wondering if anyone knew of a way to access DOS Paradox 4.5 tables in PostgreSQL. I currently have several Perl and PAL scripts that transfer data between the two systems via text, but I would _much_ rather simply be able to read and write to/from the Pardox tables from Linux. Is something

[ADMIN] starting postmaster

1999-06-30 Thread JT Kirkpatrick
i am trying to debug a locking problem in our database. i currently am starting postgres using this: '/usr/bin/postmaster -B 256 -S -D /ssms -i' i am trying to start it with the debugging option, -d 9, following the advise of a friend. but i can't get it to start. i have tried: '/usr/bin/p

[ADMIN] RE: [SQL] float4

1999-06-30 Thread JT Kirkpatrick
ahh, so 6.5 has an answer! for our "cash and accounts payable" database i converted the float4 field to int4, and altered the input mask on the front end to show a decimal point, but not save it with the data. so now i am saving $35.99 as 3599. i had to alter all reports to divide by 100. w

Re: [ADMIN] Re: vacum, locks, indicies and whatnot

1999-06-30 Thread Herouth Maoz
At 19:52 +0300 on 29/06/1999, Mark Dalphin wrote: > ... a program called AutoVac which loops over all the databases controlled by > Postgresql, drops each index, VACUUM ANALYZE each table and then re-creates > the index. An interesting mixture of shell, Perl and psql (no complaint, > mind you; i

[ADMIN] Memory exhausted in AllocSetAlloc()

1999-06-30 Thread Brian Baquiran
We had problems with postgres when using ODBC (in Acess97), this message comes out on the console: FATAL 1: Memory exhausted in AllocSetAlloc() pq_recvbuf: unexpected EOF on client connection Is there a tweak we can do? This is the 6.4 release. Thanks, Brian -- [EMAIL PROTECTED] http://www.baq