Even with a primary UPS on the *entire PostgreSQL server* does one still
need, or even still recommend, a battery-backed cache on the RAID controller
card? [ref SCSI 320, of course]
If so, I'd be interest in knowing briefly why.
Thanks.
-Original Message-
===snip===
...
every server I'
I presume this thread was all brought about by the /. article
http://developers.slashdot.org/article.pl?sid=05/10/31/0659254&tid=221&tid=1
87
According to the link provided in the /. article
(http://news.zdnet.com/2100-3513_22-5920796.html), Oracle has *proposed* a
free version by "year end". Obv
EMAIL PROTECTED]
Sent: Monday, October 31, 2005 11:50 AM
To: Wes Williams
Cc: Postgresql-General; [EMAIL PROTECTED]
Subject: Re: [GENERAL] Oracle 10g Express - any danger for Postgres?
I assume they are probably thinking of a free for non-commercial use,
which is great and all, but I assume that lik
Precisely the point I was trying to make sure everyone would understand
clearly. Although I don't have a copy of Oracle's suspected new license, if
it is close to the existing license verbiage, even though it is "crippled"
by having certain hardware and software limits, those limits are per
physic
Still, at least Oracle 10g provides for an easy GUI from which to configure
and perform imports and exports of data. Some of use have need for a
database that can dump all data and accept another series of new data...only
to be dropped again in a few days. The GUI tools make this MUCH easier -
es
Again, the previously provide link is NOT the version that is licensed free
for commercial production use!
The version in the headlines lately suggesting a free Oracle database for
professional and production use is NOT YET PUBLICLY AVAILABLE [expected by
year-end]. Still, the link below is likel
Go ahead and proceed through the click-throughs...this is still the same old
demo for development and testing only that they have had available for some
time.
This updated on Oct-28th only is for a newer
version(http://www.oracle.com/technology/software/products/database/xe/index
.html) of the sam
Correct, the default setting for PostgreSQL 8.1 W32 value in postgresql.conf
is 'autovacuum' to 'on'.
You can see this and more settings in pgAdmin III by visiting 'Tools',
'Server Configuration', then the config file of your choice.
Now, if only I could setup my home to autovaccum.
-Origin
after restarting postgresql.
Versions/Environment:Postgresql 8.1.4 (installed from ports on FreeBSD 6.1)I've already tried reinstalling the postgresql81-server and postgresql81-client ports and their dependencies via portupgrade, but the symptoms persist. What else should I try?
-- Wes Shel
t seems a little disingenuous to claim they support them on the site's front page. Oh well. (shrug)
-- Wes Sheldahl[EMAIL PROTECTED]
well. Right now it's running as pgsql, UID 70, which I'm sure is the default. Thanks,
Wes SheldahlOn 10/21/06, Marc G. Fournier <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-Hash: SHA1Are you running this in a FreeBSD jail under 6.1? It sounds like the problemthat I
obably* included among the applications you can install during the Fedora installation process itself. To install the client and server packages via yum, you would do:
yum install postgresql postgresql-serverCheers,-- Wes SheldahlSheldahl Consulting LLChttp://www.sheldahlconsulting.comPhone: 859-338-3
expirations. So this particular problem may be better solved without any timer functionality either in OR out of the database... if you did have a cron job run to check, you would probably just have it set a boolean field on expired records or something of that sort, and run it a little after midnight, at the start of each day, assuming durations were always being measured in days.
Best of luck,-- Wes Sheldahl[EMAIL PROTECTED]
On 4/30/06, Tony Lausin <[EMAIL PROTECTED]> wrote:
Hello all,
I'm working on a CMS which requires an open source database capable of
handling hundreds of thousands of users simultaneously, with a high
rate of database writes, and without buckling. We're talking somewhere
between nerve.com/catch2
EENTRANT -D_POSIX_PTHREAD_SEMANTICS"
According to Jan, -D_REENTRANT must also be specified for libpq to be built
correctly.
Why isn't -D_THREAD_SAFE required also?
Wes
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
- I have not changed those. I did bump up some postgresql.conf
memory settings, but haven't touched any of the cost parameters.
Wes
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
When I try to run thread_test.c from the CVS tip, it hangs in an infinite
CPU loop on both linux (RedHat AS 3.0, gcc 3.2.3) and Mac OS X 10.3.3 (gcc
3.3). I've also tried down to gcc 2.96 on Mac OS X.
If I compile it with -g instead of -O2 on linux, it runs to completion and
gives me:
Add this t
et too small.
I tried doing a mass update of all rows with a single SQL statement in psql
and after it ran for many hours, I got 'out of memory'. I didn't try that
using C and WITH HOLD. I assumed it ran out of swap space, but was sleeping
at the time.
101 - 118 of 118 matches
Mail list logo
