Re: [HACKERS] refusing connections based on load ...
Nathan Myers wrote: On Mon, Apr 23, 2001 at 03:09:53PM -0300, The Hermit Hacker wrote: Anyone thought of implementing this, similar to how sendmail does it? If load n, refuse connections? ... If nobody is working on something like this, does anyone but me feel that it has merit to make use of? I'll play with it if so ... I agree that it would be useful. Even more useful would be soft load shedding, where once some load average level is exceeded the postmaster delays a bit (proportionately) before accepting a connection. Or have the load check on AtXactStart, and delay new transactions until load is back below x, where x is configurable per user/group plus some per database scaling factor. How is this different than limiting the number of backends that can be running at once? It would seem to me that a user that has a delayed startup is going to think there's something wrong with the server and keep trying, where as a message like too many clients - try again later explains what's really going on. len morgan ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] RPM upgrade caveats going from a beta version to RC
Lamar Owen writes: One quick note -- since 'R' 'b', the RC RPM's must be forced to install with --oldpackage, as RPM does a simple strcmp of version numbers -- 7.1RC3 7.1beta1, for instance. Just force it with --oldpackage if you have a 7.1beta RPM already installed. Couldn't this be fixed (in future releases) with rcX and BetaX? I believe r B. len morgan ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] pgaccess: russian fonts SQL window???
1. I cannot view russian text in russian when I use pgaccess. I set all the fonts in 'Preferences' to -cronyx-helvetica-*-*-*-*-17-*-*-*-*-*-koi8-* , but don't see russian letters in 'tables' and others windows. The texts are really in russian, DBENCODING is KOI8. Hm. We've had a couple of reports recently that suggest that there's a character-set-translation problem between Postgres and recent Tcl/Tk releases --- which seems to describe your problem as well. I have an unproven suspicion that this is related to Tcl's changeover to UTF-8 internal representation, because the reports have all come from people running Tcl 8.2 or later. But no one's done the work yet to understand the problem in detail or propose a fix. Want to dig into it? regards, tom lane I have used Postgres and Tcl/Tk for quite some time and yes, when 8.2 came out, I had trouble accessing ANYTHING because of the UTF-8 switch. My solution was to upgrade my pgsql.tcl file with a new one. I tried it once and it worked but other events have prevented me from switching all of my code yet. Pgsql.tcl is a tcl source only interface to postgres (as opposed to a .dll or .so). Whether the changes in there have made it into libpgtcl.so/dll I don't know. I would be happy to forward it somewhere if you would like to try it out. len morgan
