They seem pretty clean (have patched vanilla kernels + xfs for Mandrake
9.2/9.0).
And yes, I would recommend xfs - noticeably faster than ext3, and no
sign of any mysterious hangs under load.
best wishes
Mark
Christopher Browne wrote:
Do the patches work? As far as I have heard, quite well
"Octavio Alvarez" <[EMAIL PROTECTED]> writes:
> Please tell me if this timing makes sense to you for a Celeron 433 w/
> RAM=256MB dedicated testing server. I expected some slowness, but not this
> high.
I'll bet you have foreign keys referencing this table, and the
referencing columns do not have
Hi,
Sorry for the long e-mail. Here is a summary of my questions:
I am running osdl-dbt1 against pgsql-7.3.3. The result is at:
http://khack.osdl.org/stp/286627/
1. Based on the hardware and software configuration, does my database
configuration make sense?
2. Is 'defining a cursor and fetch m
You can do snapshots in FreeBSD 5.x with UFS2 as well but that (
nor XFS snapshots ) will let you backup with the database server
running. Just because you will get the file exactly as it was at
a particular instant does not mean that the postmaster did not
still have some some data that was not
Orion Henry <[EMAIL PROTECTED]> writes:
> The queries usually are in the form of, where "user_id = something and
> event_time between something and something".
> Half of my queries index off of the user_id and half index off the
> event_time. I was thinking this would be a perfect opportunity to
Octavio Alvarez wrote:
Please tell me if this timing makes sense to you for a Celeron 433 w/
RAM=256MB dedicated testing server. I expected some slowness, but not this
high.
Well delete is generally slow. If you want to delete the entire table
(and your really sure)
use truncate.
J
db_eps
Please tell me if this timing makes sense to you for a Celeron 433 w/
RAM=256MB dedicated testing server. I expected some slowness, but not this
high.
db_epsilon=# \d t_active_subjects
Table "public.t_active_subjects"
Column | Type |
Well, I'd point to one major factor with RHAT; they employ Stephen
Tweedie, creator of ext3, and have been paying him to work on it for
some time now. If they _didn't_ promote use of ext3, they would be
very much vulnerable to the "won't eat their own dogfood" criticism.
True but frankly, they
[EMAIL PROTECTED] ("Joshua D. Drake") writes:
>>Yes, I guess I shoulda thought of that, eh? Thanks. The docs do
>>suggest that there are some significant differences between the two
>>versions of the filesystem, so I'm not sure how sanguine I'd be about
>>the degree of "testing" the filesystem ha
Yes, I guess I shoulda thought of that, eh? Thanks. The docs do
suggest that there are some significant differences between the two
versions of the filesystem, so I'm not sure how sanguine I'd be about
the degree of "testing" the filesystem has received on Linux. On the
Well SuSE ships with
On Fri, Jan 23, 2004 at 11:05:41AM -0800, Joshua D. Drake wrote:
> http://oss.sgi.com/projects/xfs/
Yes, I guess I shoulda thought of that, eh? Thanks. The docs do
suggest that there are some significant differences between the two
versions of the filesystem, so I'm not sure how sanguine I'd be
There is nothing else on Linux that comes close to that. Plus XFS has been
proven in a 64 bit environment (Irix).
I had lots of happy experiences with XFS when administering IRIX
boxes[1], but I don't know what differences the Linux port entailed.
Do you have details on that?
http://oss.s
On Fri, Jan 23, 2004 at 10:18:35AM -0800, Joshua D. Drake wrote:
> >
> Not I. We have had issues with JFS and data corruption on a powerout but
> XFS has been rock solid in all of our tests.
Sorry, it was Josh Berkus:
http://archives.postgresql.org/pgsql-performance/2004-01/msg00086.php
> There
I've got a table with about 10 million events in it.
Each has a user_id (about 1000 users) and a event_time timestamp
covering a 4 year period with about 50% of the events being in the last
year. Some users have only dozens of events. A few have hundreds of
thousands.
The queries usually are in
XFS.. hands down.
I thought it was you who recently said you thought there was some
sort of possible caching problem there?
Not I. We have had issues with JFS and data corruption on a powerout but
XFS has been rock solid in all of our tests.
XFS also has the interesting ability (although I
On Fri, Jan 23, 2004 at 08:51:03AM -0800, Joshua D. Drake wrote:
>
>
> XFS.. hands down.
I thought it was you who recently said you thought there was some
sort of possible caching problem there?
A
--
Andrew Sullivan | [EMAIL PROTECTED]
The plural of anecdote is not data.
--Ro
A few question regarding PostgreSQL handling of queries:
- Is each query submitted parsed and planned even if it is identical to a
query submitted before?
For example, 10 queries "select * from animals where id=:b1" with possibly
different bind variable :b1 values will be fully processed (parse
Dave Thompson wrote:
Hello All
Just wanted to gather
opinions on what file system has the best balance between performance
and reliability when used on a quad processor machine running SuSE64.
Thanks
XFS.. hands down.
DAve
--
Command Prompt, Inc., home of Mammot
Hello All
Just wanted to gather opinions on what
file system has the best balance between performance and reliability when used
on a quad processor machine running SuSE64. Thanks
DAve
D'Arcy J.M. Cain wrote:
> With the price of GigE adapters I wouldn't consider anything else.
>
> I have a huge database that takes about an hour to copy. The netApp snapshot
> feature is very nice because I can get a "moment in time" image of the
> database. Even though I can't run from the sn
Hello
try prepared statements, PQexecPrepared
http://developer.postgresql.org/docs/postgres/libpq-exec.html
Regards
Pavel Stehule
On Thu, 22 Jan 2004, pginfo wrote:
> Hi,
>
> thanks for the answer.
> It is very interest, because I readet many times that if I write the trigger
> in "C" it will
21 matches
Mail list logo
