There is something wonky on this mail list. I did not send this.
-Original Message-
From: Gregory S. Williamson
Sent: Fri 6/11/2004 2:10 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject:Re: [GENERAL] Trying to minimize the impact of checkpoints (resend)
In-reply-
I would very much like to see the same test with Fsync on.
A test that does not reflect real-world use has less value than one that
just shows how fast it can go.
>
> For a read-only database, fsync could be turned off. For any other
> system it would be hair-brained and nobody in their right mind
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Steve Wolfe
> Sent: Thursday, June 10, 2004 2:09 PM
> To: pgsql-general
> Subject: [GENERAL] Opteron scaling with PostgreSQL
>
>
>
>Some time ago, I asked about how well PostgreSQL scales with th
Hi,
I am just wondering if bytea functions (byteaeq, byteage,byteagt,...) will
be included in the offical document and assumed to be supported in future
release.
For now, I could only find them in release 7.2 note.
Your confirmation reply is appreciated.
Thanks!
Eric
ps.Is this the right place to
[EMAIL PROTECTED] writes:
> I'm using PostgreSQL 7.3.4 on RH9. Data and logs are on separate
> disks. (These are low-end IDE disks. That part of the problem
> is out of my control.)
> When a checkpoint occurs, all operations slow way, way down.
Not too surprising; you haven't got enough I/O bandw
[EMAIL PROTECTED] writes:
> Does anyone have any experience in modifying the priority of the
> checkpoint process itself, (re-nicing it)?
Unfortunately for you, re-nicing doesn't generally affect a processes
I/O rate--it's meant for CPU-bound processes.
It might be possible to add code to "throt
[Sorry if this is a repeat. I think the first message may have
been rejected due to an attachment.]
I'm using PostgreSQL 7.3.4 on RH9. Data and logs are on separate
disks. (These are low-end IDE disks. That part of the problem
is out of my control.)
When a checkpoint occurs, all operations slow w
Hello list,
Apologize first if this is off topic.
have this function in plpgsql
DECLARE
crow histmer%rowtype;
BEGIN
select * into crow from histmer
where fecha = date 'now';
if found then
return next crow;
end if;
select * into crow fr
"Eric Lu" <[EMAIL PROTECTED]> writes:
> I am just wondering if bytea functions (byteaeq, byteage,byteagt,...) will
> be included in the offical document and assumed to be supported in future
> release.
We generally do not bother to document functions that are only meant to
support operators. Use
[EMAIL PROTECTED] writes:
> if i understand right, after some time vacuum must run without
> warnings, but after first warning vacuum print this warnings every
> time until reindex.
Oh? I was thinking of transient conditions, but it sounds like you
have found a way to produce a permanent mismatc
[EMAIL PROTECTED] writes:
> Can I take the INFORMATION SCHEMA views from 7.4 and install them in older
> versions of PostgreSQL, if so, how far back can they work?
I doubt they would just drop in, but you could possibly adapt them
to mostly work...
regards, tom lane
-
[EMAIL PROTECTED] wrote:
> Can I take the INFORMATION SCHEMA views from 7.4 and install them in
> older versions of PostgreSQL, if so, how far back can they work?
No. For your purposes, you maybe be able to backport them and
distribute the altered versions with your product. For some cases this
Quoting [EMAIL PROTECTED]:
> When a checkpoint occurs, all operations slow way, way down.
> The attached spreadsheet (xls file, prepared in OO so unlikely
> to be dangerous) shows a run of a few hours, and the various spikes
> every 25-30 minutes seem consistent with checkpointing. The
> applicat
This will be fixed on Solaris in PostgreSQL release 7.4.3.
---
Wes Palmer wrote:
> On 3/23/04 8:28 PM, "Bruce Momjian" <[EMAIL PROTECTED]> wrote:
>
> > If I had to take a guess, there is something wrong with the ecpg progra
I have been using Postgresql 7.2.4 on a Redhat 8.0 system. Prior to
putting the system into production I want to upgrade Postgresql and PHP
to the latest stable versions.
To that end I have downloaded the latest versions and compiled them. I
have saved my current databases using pg_dumpall.
Cur
My name is Mike Griffin and we are adding PostgreSQL support to our
product, MyGeneration. MyGeneration pulls meta-data from DBMS systems to
generate business objects and stored procedures and such.
We are using the .NET managed provider Npgsql.dll. We typically get meta
data from OleDb providers
Hi,
On Fri, 11 Jun 2004, [iso-8859-1] zhicheng wang wrote:
> can any one recommend a good postgresql training
> course in the UK. thanks
http://techdocs.postgresql.org/companies.php
Some companies provide training courses for PostgreSQL.
Regards,
--
Devrim GUNDUZ
devrim~gunduz.org
Dennis Breithaupt wrote:
Hy all,
I request your support for the following problem. (with "postmaster
(PostgreSQL) 7.4.1")
On a development-system I lost the pg_xlog-directory due to a system
crash, where the physical device on which the mountpoint pg_xlog was
located got broken.
[...]
...in th
Hy all,
I request your support for the following problem. (with "postmaster
(PostgreSQL) 7.4.1")
On a development-system I lost the pg_xlog-directory due to a system
crash, where the physical device on which the mountpoint pg_xlog was
located got broken.
LOG: could not open file
"/usr/local/
dear all
can any one recommend a good postgresql training
course in the UK. thanks
cheng
=
Best wishes
Z C Wang
___ALL-NEW Yahoo! Messenger -
so many all-new ways to express yourself http://uk.me
>> look please http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253295
TL> I wouldn't worry about it. It's probably due to the fact that we tend
TL> to release write lock on system catalogs immediately after updating the
TL> catalog, instead of holding the lock till commit.
ok, but what is best:
El Jue 10 Jun 2004 22:14, escribió:
> Hi,
>
> we are using Postgres with a J2EE application (JBoss) and get
> intermittent "out of memory" errors on the Postgres database. We are
> running on a fairly large Linux server (Dual 3GHz, 2GB Ram) with the
> following parameters:
>
> shared_buffers = 8192
Mark Striebeck wrote:
Hi,
we are using Postgres with a J2EE application (JBoss) and get
intermittent "out of memory" errors on the Postgres database. We are
running on a fairly large Linux server (Dual 3GHz, 2GB Ram) with the
following parameters:
shared_buffers = 8192
sort_mem = 8192
effective
23 matches
Mail list logo
