.
I put a stub page in at http://wiki.postgresql.org/wiki/Pgpass to cover
this whole area but never really filled it in. I'd prefer seeing that get
fleshed out and then the automation page can just link to it, because this
is a very FAQ.
--
* Greg Smith [EMAIL PROTECTED] http://www.gre
Y, though, those will probably just
slow you down.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
hanks,
--greg
#x27;ve got RAM to waste it doesn't really matter if you set it too high
though.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
l.org/wiki/Bulk_Loading_and_Restores
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
r later, you can set archive_timeout to bound how
long it will take before that last segment shows up, or you can manually
call pg_switch_xlog. See http://wiki.postgresql.org/wiki/Warm_Standby for
how to force that on 8.1 (and the walkthrough on that page may be helpful
to you as well).
--
* Greg Smith [E
listed at
http://wiki.postgresql.org/wiki/Using_EXPLAIN and the primary things to
tune in the postgresql.conf are described at
http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general ma
systems that benefit some from security by obscurity, and if you can know
the method used that usually allows an even easier approach.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
tasts to make the caches clear, the only easy
way to make things more clear is to reboot the whole server.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://
ite writes, which
would make this problem go away--might even auto-tune checkpoint_segments
or replace it altogether with an implementation based on those inputs.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgres
On Mon, 29 Sep 2008, Sam Mason wrote:
On Mon, Sep 29, 2008 at 02:55:52AM -0400, Greg Smith wrote:
3) sudo echo 3 > /proc/sys/vm/drop_caches
I'm not sure about the rest, but shouldn't this be:
echo 3 | sudo tee /proc/sys/vm/drop_caches
I couldn't think of any reason to ac
w instead is what the big tables
and indexes in your database are to figure out what is gobbling space.
The script at http://wiki.postgresql.org/wiki/Disk_Usage will give you
that.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgs
TECTED] for the
last code submission there and
http://wiki.postgresql.org/wiki/In-place_upgrade for an outline of the
project.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to yo
ssing ncurses-devel on CentOS 5. (search search search) Ah, here's
an example that looks like yours that says the same thing:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg07533.html
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general ma
rst, and only if you don't get anything useful back after a
wait should you submit your question to a second list.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
nd
worst RAM I tried on a single motherboard recently.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
is. If you're CPU limited for example, you'd want
to stay away from compression; if I/O limited that might make sense.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
re on this topic into a Wiki article anyway, which
will pull the good stuff out of here regardless of the originating list.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subs
the
next release comes out; when that comes up I can point to this thread as a
reminder of why that's needed.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
or compared fairly.
Anyway making easier to tune PostgreSQL even if not optimally would
be a good target.
There were two commits to the core PostgreSQL server code last month aimed
at making it easier to build tools that interact with the server
configuration. The tool(s) that u
ll get to that myself eventually even if nobody else
does, as this is a recurring problem I'd like to make go away.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Wed, 15 Oct 2008, Gregory Stark wrote:
Greg Smith <[EMAIL PROTECTED]> writes:
DB2 has automatically updated the "shmmax" kernel
parameter from "33554432" to the recommended value "268435456".
This seems like a bogus thing for an applica
y server, so the WAL files will be forwarded to another
server.
If you're keeping a warm-standby server around, the loss of a database
disk might not be as big of a problem--you can keep that fairly up to
date. Really depends on what the business guarantees required are.
--
* Greg Smith [EM
he settings here are weird, it does annoy me a bit
anytime I stop to think about it though.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresq
e-mail pedantry
arguments was broken recently anyway, when I had someone I'm compelled to
communicate with regularly complain that they couldn't follow my
top-posted messages and requested me to reply "like everybody else" to
their mail in the future.
--
* Greg Smith [EMAIL
ives/30-Lost-time.html
for an example.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
messages
are approved as list-worthy (attachments aren't too big, etc.) and when
"resend" is called to implement the same feature: add or extend the
reply-to with the list address while not losing any explicit reply-to in
the original. But I think you still have to hack it
e who actually looked at the header of my messages to see what I use.
Or perhaps start a flamewar with those deviant mutt users; that would be
about as productive as the continued existence of this thread.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-ge
commitfest for inclusion into 8.4; it's really essential for a
WAN-based PITR setup and it would be nice to include it with the
distribution.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
y to just download and use.
That's why I'd like to see it turn into a more official contrib module, so
that it will never lose sync with the page header format and be available
to anyone using PITR.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent
done (so you don't do it for a segment twice) and a way to turn it off so
everybody doesn't go through that overhead (which probably means another
GUC). That's a bit much trouble to go through just for a feature with a
fairly limited use-case that can easily live outside of the
circa 8.2: the software is available, and it works, but it
seems kind of sketchy to those not familiar with the source of the code.
Bundling it into the software as a contrib module just makes that problem
go away for end-users.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Bal
hat's why I didn't care when this got kicked out of the March
CommitFest; was hoping a better one would show up. But if 8.4 isn't going
out the door with the feature people really want, it would be nice to at
least make the stopgap kludge more easily available.
--
* Greg Smith [E
is just prolonging the
downtime). Once you've gotten some ideas for what to look at, like the
little script above, you have to make the users wait until you're done
running that before giving into pressure to fix something. Otherwise
you'll never solve the problem.
--
* Greg
ittle heavy (was
hoping for an "alias"-sized answer) to figure out something that the
server certainly knows.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
appreciated, I'll hack together
something that works. And now that I know it's not just me I'll see if I
can expose this in a future patch.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
x27;s safe to run
analysis on the old file because it's complete.
I can think of some better ways to slice that switching time downward
(NOTIFY comes to mind), but I'd bet most admins wouldn't use a more
sophisticated one even if it were available--too much work compared to
somethi
96f6dea948021ddfc9f0f5a38
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ut of
memory; that's a really high setting. Generally, if it's only a report or
two that need a lot more working memory for sorts, you can do this at the
beginning of them instead:
set work_mem='512MB';
Which will set the value only for that session.
--
* Greg Smi
rom source rather than fooling with the
official pacakges. I would wager it will take you less time to figure out
how to do that than to fight these experimental packages into submission.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing l
ck is write speed on the intermediate results mentioned, then it
may very well be the case that the best way to accelerate this workload is
with a RAM-based tablespace. But in some cases tuning shared_buffers and
work_mem way upwards is all it takes.
--
* Greg Smith [EMAIL PROTECTED]
ver updating you could try
100). I doubt that will be anything but a minor incremental improvement
though.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
xample there, it
shows what a streaming query similar to the requirements here would look
like: an average and other statistics produced on a per-interval basis.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresq
do most of the research I was considering for me?
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ecifically after my backup tapes."
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
columns. You could do something like create index i
on (point(col1,col2)) though I think you might have to actually make a
"box" instead. Alternatively you could look at the "cube" contrib
module. As far as i know all of these actually work with doubles
though, so you'll lose
even without the RECURSIVE
keyword, which is apparently just a noise word in Oracle.
--
greg
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
bused recovery a bit leading up to here. This might be a full disk or a
bad block on the xlog drive instead of something more complicated.
--
* Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make ch
quot; and hopefully more
than pretty much all have a lock of this type -- *all* transactions
start with a lock on their own transaction id and hold it until they
finish. That's how other transactions wait for a transaction to
finish, by attempting to get a lock on the transaction id of the
transa
On Mon, 9 Nov 2009, Richard Broersma wrote:
Out of curiosity, what are the favorite editor for authoring the
PostgreSQL document sgml files?
http://developer.postgresql.org/pgdocs/postgres/docguide-authoring.html
--
* Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD
er to set up.
It's always worth having the dump, even if you also implement PITR.
The dump allows you to restore just specific tables or to restore onto
a different type of system. The PITR backup is a physical
byte-for-byte copy which only works if you restore the whole database
and only o
out the one
project like this I did, that featured a shared SAN and commercial
cluster software.
--
Greg Smithg...@2ndquadrant.comBaltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
spikes upwards. If you don't expect a standby is going to be able to
keep up with your volume due to that issue, the remote one is going to
be even worse though.
--
Greg Smithg...@2ndquadrant.comBaltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
ter a
crash on the original node. The thing you cannot let happen is allowing
the original master to continue writing to the shared SAN volume once
that transition has happened.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2nd
er to the slave system in order to recovery from
a failure, and that list will go back to when you started the backup.
Saving those is actually part of the base backup process, as documented
in the manual if you read that section more carefully.
--
Greg Smith2ndQuadrant Baltimore, MD
ouble a bit (but not completely).
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresq
ssociated libraries, so they
might either have to add those to the system loader configuration or set
LD_LIBRARY_PATH before calling database binaries. Ideally you'd find
them via rpath or something so this isn't an issue, but it's easy to
miss that the first time you make a change lik
at in a script,
you might need to setup a .pgpass file:
http://www.postgresql.org/docs/current/static/libpq-pgpass.html
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-ge
the indexes better than vacuum does.
--
greg
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
hrunk, you might be able to work your
way up to bigger ones.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscrip
and instead just mention it as another option during the pg_ctl lesson,
that would be one less thing to have to train on.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list
bedded in various packagers' initscripts. And
I thought the entire point of this proposal was that we could expunge
knowledge of initdb from users' minds.
Exactly. I think the best transition design would be to make "initdb"
and "init" both work.
--
Greg Smith2
s/8.4/interactive/libpq-pgpass.html
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
t come with the database. As you
can see at http://www.linbrary.com/postgresql/840/index.html "Fultus
Corporation is not affiliated with
The PostgreSQL Global Development Group."
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.
th in
8.4, like having the background writer active during recovery, that
should help on I/O bound slaves.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-general@postgres
the backup to be useful. The
standby doesn't actually use it for anything, it's more of a helper for
a human trying to figure out what's going on.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
rt order that the results are ordered in.
Incidentally you probably want UNION ALL rather than UNION in the
original query.
--
greg
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Wed, Nov 25, 2009 at 2:00 AM, Konstantin Izmailov wrote:
> Greg,
> this is brilliant - thank you very much!
>
> Is "partition by" compatible to PostgreSQL 8.0/8.2? I could not find
> compatibility information. It works fine with PG 8.3/8.4 and Greenplum 3.3
> thou
a more focused recommendations for where you
can find it.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your sub
ty, so a
source build may be the only good route to get a newer version onto there.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
tep of the build the last
time. If you're not sure exactly how the old one was built, this can
help you out.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-genera
rectory or ship with a
startup script which puts that directory in LD_LIBRARY_PATH. Whether
you want to append, leaving the system directories ahead of the
one-click installed libraries, or prepend so the linker always uses
your libraries would depend on how you want it to behave. Setting
rpath is equiva
d expensive memory is one you can't spend on disks
instead, so in reality AMD's cost effectiveness can make for a better
overall database system at the same price point. If you really need a
lot of disks to make your app performance well, better to focus on that
rather than tr
the spawned psql process and use that to lookup the
backend pid assigned; not hard to do if you've seen an example or know
how this all fits together, but not really an obvious technique either.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndqu
river too. In this case it seems more likely it's a drive failure
though.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
place/to/save/pid';
Not so useful if there's more than one of the query running at once, but
in the "nice a batch job" context it might be usable.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
Craig Ringer wrote:
On 1/12/2009 11:33 AM, Greg Smith wrote:
1) If you spawn the psql process with bash using "&", you can then find
its pid with "$!", then chain through the process tree with ps and
pg_stat_activity as needed to figure out the backend pid.
I feel li
k on Linux too. Since you're on Solaris, you should be
able to get the smaller open_datasync writes and some improvements from
using direct writes too stack on top of one another.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com ww
e to avoid using Linux's LVM for
similar reasons--while it shouldn't be so slow, it is. Nothing you can
do about it but use direct disk partitions instead if you need the
performance to be good.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
See the data type "SERIAL" in the PostgreSQL manual for whatever flavor of the
database you are using ...
Apologies for top-posting -- challenged mail client.
HTH,
Greg W.
From: Andre Lopes
To: pgsql-general@postgresql.org
Sent: Wed, December 2,
nless you paid them to. You'd need a much better
justification for why you can't just filter things out of the log
yourself before it would be worth further complicating the code
involved. It's just not a common request--if anything, you might find
people want everything
;, "high availability", "change management",
"postgres upgrades", etc.
--
greg
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
rnative would be to just store them in byteas and then handle
sorting and displaying by calling the conversion procedure on the fly.
--
greg
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
.
Here's how to clear the OS cache on Linux:
|sync; echo 3 > /proc/sys/vm/drop_caches|
And on Windows you should be able to clear it with CacheSet:
http://technet.microsoft.com/en-us/sysinternals/bb897561.aspx
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Serv
as well figure out how to only compute the summarized version
once. The last comment in this thread as I write this, from Grzegorz,
suggests one approach for something like that.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com w
lls happen. I'm not
sure how to do this on OS X though.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes t
statements/second are committing,
which is basically just a tiny write to the WAL followed by an fsync.
That's basically the fsync rate of the system, as long as you don't get
a checkpoint in the middle slowing it down.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, S
t wait for completion before
returning success, the original criteria. If you're naive and believe
that anything the drive has said is written is actually on disk, which
used to be how things worked, from that perspective all (well, almost
all) drives lie. Having that behavior documented a
break them into a separate, optional package, but
they're nonetheless part of the official source code release.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-ge
not too familiar with this area
because recommendation #1 if I ran into this situation would be "Don't
try that on OS X with HFS+". Maybe there's some way to get more
performance out of there by tweaking the OS, I haven't had to do so
myself enough to know the details off t
of
data loss, but not the risk of corruption that turning fsync off
altogether does. Basically, it reduces the number of fsync's from
transaction commits to be a fixed number per unit of time, rather than
being proportional to the number of commits.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
monitoring app too; great. That's only helpful if you get the basics
right first.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
Dave Page wrote:
On Fri, Dec 11, 2009 at 9:02 AM, Massa, Harald Armin wrote:
I got MUCH better results by drastically lowering shared_buffers on
Windows. Drastically = 8MB.
Wow - really? Greg and I did some rough pgbench experiments last year
and were finding the on a 4GB machine
SQL to build in Eclipse that might help
you out: http://wiki.postgresql.org/wiki/Working_with_Eclipse
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
comparing was Ubuntu - which I
know from personal experience has very poor default settings for
shared_buffers due to Ubuntu's operating system defaults. Perhaps if
theses parameters were altered postgres would get a clean sweep.
The parameters are no better on a default Windows ins
://wiki.postgresql.org/wiki/Replication%2C_Clustering%2C_and_Connection_Pooling
, with more details about some of the projects/products that add
features in this area at http://wiki.postgresql.org/wiki/Clustering
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g
s. A large number of the tunables recommend to
tweak there mainly impact query execution time.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
with an E-SATA connector on them. That's the only
even remotely reliable external drive solution nowadays, because at
least you're guaranteed to get SMART data, cache flushes, and a drive
technology that's always been optimized for ruggedness.
--
Greg Smith2ndQuadrant B
Michael Clark wrote:
On Wed, Dec 16, 2009 at 11:25 AM, Greg Smith <mailto:g...@2ndquadrant.com>> wrote:
Florian Weimer wrote:
I hope that Mac OS X turns off write caches on low battery.
I've never heard of such a thing. The best you can do is try t
has less corruption issues IMHO is
that there's exactly one "storage engine" and everybody works on it.
What the MySQL community calls options in storage engines I call split
QA, and the source of new types of failures not possible if you only
have one underlying storage codebase to worr
701 - 800 of 1774 matches
Mail list logo
