doesn't really make that big of a difference.
My recommendation, each database gets it's own aggregate unless the
IO footprint is very low.
Let me know if you need more details.
Regards,
Dan Gorman
On Jul 11, 2007, at 6:03 AM, Dave Cramer wrote:
Assuming we have 24 73G drives is it bett
No, however, I will attach the postgreql.conf so everyone can look at
other settings just in case.
postgresql.conf
Description: Binary data
Regards,
Dan Gorman
On Jun 25, 2007, at 10:07 AM, Gregory Stark wrote:
"Simon Riggs" <[EMAIL PROTECTED]> writes:
WARNING: page 2
you guys would like me to try to 'break' it again and keep the db
around for further testing let me know.
Regards,
Dan Gorman
On Jun 25, 2007, at 9:34 AM, Tom Lane wrote:
Dan Gorman <[EMAIL PROTECTED]> writes:
Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [9-1] 2007-06
Greg,
PG 8.2.4
Regards,
Dan Gorman
On Jun 25, 2007, at 9:02 AM, Gregory Stark wrote:
"Dan Gorman" <[EMAIL PROTECTED]> writes:
I took several snapshots. In all cases the FS was fine. In one
case the db
looked like on recovery it thought there were outstanding pages
t
I took several snapshots. In all cases the FS was fine. In one case
the db looked like on recovery it thought there were outstanding
pages to be written to disk as seen below and the db wouldn't start.
Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [9-1] 2007-06-21
00:39:43 PDTLOG: redo
It's the latter, is snapshot of the durable state of the storage
system (e.g. it will never be corrupted)
Regards,
Dan Gorman
On Jun 22, 2007, at 11:02 AM, Tom Lane wrote:
"Simon Riggs" <[EMAIL PROTECTED]> writes:
On Fri, 2007-06-22 at 13:12 -0400, Tom Lane wrote:
If
Ah okay. I understand now. So how can I signal postgres I'm about to
take a backup ? (read doc from previous email ? )
Regards,
Dan Gorman
On Jun 22, 2007, at 4:38 AM, Simon Riggs wrote:
On Fri, 2007-06-22 at 04:10 -0700, Dan Gorman wrote:
This snapshot is done at the LUN (filer)
This snapshot is done at the LUN (filer) level, postgres is un-aware
we're creating a backup, so I'm not sure how pg_start_backup() plays
into this ...
Regards,
Dan Gorman
On Jun 22, 2007, at 3:55 AM, Simon Riggs wrote:
On Fri, 2007-06-22 at 11:30 +0900, Toru SHIMOGAKI wrote:
Here is an example. Most of the snap shots worked fine, but I did get
this once:
Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [9-1] 2007-06-21
00:39:43 PDTLOG: redo done at 71/99870670
Jun 21 00:39:43 sfmedstorageha001 postgres[3506]: [10-1] 2007-06-21
00:39:43 PDTWARNING: page 28905
Some of our databases are doing about 250,000 commits/min.
Best Regards,
Dan Gorman
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Currently I have jumbo frames enabled on the NA and the switches and
also are using a the 32K R/W NFS options. Everything is gigE.
Regards,
Dan Gorman
On Jun 14, 2006, at 10:51 PM, Joe Conway wrote:
Dan Gorman wrote:
That makes sense. Speaking of NetApp, we're using the 3050C with 4
That makes sense. Speaking of NetApp, we're using the 3050C with 4 FC
shelfs. Any generic advice other than the NetApp (their NFS oracle
tuning options)
that might be useful? (e.g. turning off snapshots)
Regards,
Dan Gorman
On Jun 14, 2006, at 10:14 PM, Jonah H. Harris wrote:
On 1
rites
to via the NVRAM can I safely turn fsync off to gain additional
performance?
Best Regards,
Dan Gorman
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
know if the postgres team is working on this?
(btw, I pasted in the wrong oracle query lol - but it can be done in
mysql and oracle)
Best Regards,
Dan Gorman
On May 23, 2006, at 11:51 AM, Simon Riggs wrote:
On Tue, 2006-05-23 at 11:33 -0700, Dan Gorman wrote:
In any other DB (oracle
t you want by other means ...Details?I gather you cannot just time the app that's doing the selects,nor extract those selects and run them via psql and time themon their own? Dan Gorman wrote: All,I might be completely crazy here, but it seems every other database exposes select query stats. Pos
What I am looking for is that our DB is doing X selects a min.
Turning on logging isn't an option as it will create too much IO in
our enviornment.
Regards,
Dan Gorman
On May 23, 2006, at 11:15 AM, Mischa Sandberg wrote:
Dan Gorman wrote:
All,
I might be completely crazy here, b
All,
I might be completely crazy here, but it seems every other database
exposes select query stats. Postgres only exposes updates/deletes/
inserts. Is there something I am missing here?
Best Regards,
Dan Gorman
---(end of broadcast)---
TIP
So do NAS's
Dan
On Apr 27, 2006, at 6:42 AM, Ketema Harris wrote:
The SAN has the snapshot capability.
On 4/27/06 9:31 AM, "Bruno Wolff III" <[EMAIL PROTECTED]> wrote:
On Thu, Apr 27, 2006 at 09:06:48 -0400,
Ketema Harris <[EMAIL PROTECTED]> wrote:
Yes, your right, I meant not have to do
and I would stay away from iscsi.
Regards,
Dan Gorman
On Apr 26, 2006, at 7:35 PM, Steve Wampler wrote:
On Wed, Apr 26, 2006 at 10:06:58PM -0400, Ketema Harris wrote:
I was wondering if there were any performance issues with having a
data
directory that was an nfs mounted drive? Say like a
ting about 40-50MB/s on a PV with 14 disks on a RAID10 in
real world usage. (random IO and fully saturating a Dell 1850 with 4
concurrent threads (to peg the cpu on selects) and raw data files)
Best Regards,
Dan Gorman
On Feb 24, 2006, at 4:29 PM, Mark Kirkwood wrote:
Luke Lonergan wrote:
I&
20 matches
Mail list logo
