pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
To: 'Bruce Momjian' <maillist@candle.pha.pa.us>
To: 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>
Cc: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: 'pgsql-admin@hub.org' <pgsql-admin@hub.org>
Subject: RE: [ADMIN] RE: [SQL] float4
Date: Thu, 1 Jul 1999 08:38:41 -0400
Message-ID: <01BEC39D.1FE5FAC0.jt-kirkpatrick@mpsllc.com> (raw)

we turned OFF "use declare / fetch" on all clients odbc, and at the same 
time upped buffers in postmaster to 512.  we are no longer locking!  i 
think it was the declare/fetch thing.  i have the front end, for the most 
part, limiting users to a small number of records being transferred.  i 
watched debug as a user (only one on) selected ONE record.  the server sat 
there and processed many many many fetch 100's.  i turned it off on her 
machine, and it did only exactly what she asked it to do -- select one 
record.  now some users run large reports that pull from lots of records -- 
they have to have declare/fetch on or they overload client machine memory 
and access97 quits responding (so ctrl alt del and end-task. . .).  looks 
fairly stable now, although i'd like to have the declare/fetch turned on 
somehow by the front-end if the user selected a certain long report, and 
not by the user who could / WILL forget to turn it off for normal use. . .

thanks for everyone's help!

jt / mpsllc.com

-----Original Message-----
From:	Bruce Momjian [SMTP:maillist@candle.pha.pa.us]
Sent:	Wednesday, June 30, 1999 11:29 PM
To:	JT Kirkpatrick
Cc:	'Tom Lane'; 'pgsql-admin@hub.org'
Subject:	Re: [ADMIN] RE: [SQL] float4

> 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. 
 works
> fine.  i'd really like to get it sincerely stable in 6.4.2 before 
upgrading
> to 6.5, unless a reason for instability is solved in 6.5.  we are still
> having problems with it locking up daily. . .

Very likely fixed in 6.5.  People are reporting 6.5 as more stable.
--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026




view thread (5+ messages)

Message-ID: <01BEC39D.1FE5FAC0.jt-kirkpatrick@mpsllc.com>
Permalink:  ../01BEC39D.1FE5FAC0.jt-kirkpatrick@mpsllc.com/
Also on:    postgresql.org/message-id/01BEC39D.1FE5FAC0.jt-kirkpatrick@mpsllc.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: jt-kirkpatrick@mpsllc.com, maillist@candle.pha.pa.us, pgsql-interfaces@hub.org, tgl@sss.pgh.pa.us, pgsql-admin@hub.org
  Subject: RE: [ADMIN] RE: [SQL] float4
  In-Reply-To: <01BEC39D.1FE5FAC0.jt-kirkpatrick@mpsllc.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox