es), which
means the drive is being cooked and will likely wear out quickly. But
that won't slow it down, and you'd get much scarier messages out of smartd
if the drives had a real problem. You should improve cooling in this case
if you want to drives to have a healthy li
er, haven't needed or wanted to reboot since then:
megaraid cmm: 2.20.2.6 (Release Date: Mon Mar 7 00:01:03 EST 2005)
megaraid: 2.20.4.6-rh2 (Release Date: Wed Jun 28 12:27:22 EST 2006)
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
even worse
under SW RAID than what you get from a single disk, because you may have
to wait for multiple discs to spin to the correct position and write data
out before you can consider the transaction complete.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
nes
like bonnie output (there are certainly two sides with valid points in
that debate), to make them more compatible with flow-impaired clients, you
can't expect that mail composition software is sophisticated enough to
allow doing that for one section while still wrapping the rest of the te
ts
you're seeing, expecially when combined with a 20% greater raw CPU clock.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.post
subsystems will
shift which optimizations are useful and which have minimal impact even if
the processor is basically the same.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 6: explain
rovement) for the pgbench 1.45 that comes with
current Postgres 8.1 versions.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
I/O as the main driver of performance.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 6: explain analyze is your friend
fferent as soon as the number of
transactions increases. With little or no actual disk writes, you should
expect results to be ranked by CPU speed.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
eful on current gen multi-processor/core systems.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
#x27;ve noticed the same thing and have been meaning to figure out what the
cause is. It's just doing a select in there; it's not even in a begin/end
block.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)
into the mix people test. That one may
stack usefully with -O2, but probably not with -O3 (3 includes
optimizations that increase code size).
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 5:
y is.
Trying to do "INSERT INTO Messages(path, msgid) SELECT (path, msgid)
FROM tmpMessages" took a really long time before psql died with an
out-of-memory error.
Do you have the exact text of the error? I suspect you're falling victim
to the default parameters being far too l
imeout.it_value.tv_usec = PGSTAT_STAT_INTERVAL % 1000;
Change it to match the current line in the CVS tree for 8.3:
write_timeout.it_value.tv_usec = (PGSTAT_STAT_INTERVAL % 1000) * 1000;
That's all it took to resolve things for me.
--
* Greg Smith [EMAIL PROTECTED] http://www.
not sure how that factor may have
skewed this particular bit of data.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
elps ferret out when this happens.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PRO
at fact that today's
consumer processors produce massively more heat than those of even a few
years ago has contributed to drive manufacturers moving their specs
upwards as well.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
-
h, but I doubt
that's a problem for you if you're so brazen as to turn off fsync.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 6: explain analyze is your friend
ow
magically solve these problems.
If the key is a integer, it's always possible to figure out a trivial map
that renumbers the entire database programmatically in order to merge two
sets of data.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
given all
available information at the time. The funny thing about unexpected
changes to a business model is that you never expect them.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 9: In ver
abase. Try increasing that to 30, restart the server, and
rebuild the index to see how much the 1GB case speeds up. If it's
significantly faster (it should be), try the 5GB one again.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
-
On Mon, 23 Apr 2007, Scott Marlowe wrote:
I honestly kinda wondered if the original post came out of a time warp,
like some mail relay somewhere held onto it for 4 years or something.
That wouldn't be out of the question if this system is also his mail
server.
--
* Greg Smith [
iently before you get to the point where the database I/O is being
measured usefully at all via pgbench.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner w
nce isn't as big as it used to be.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ot data in it, and preferably after it's been running under load for a
while, and make your recommendations based on all that information.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 7: Y
esult
3) Unfair comparison of PostgreSQL with robust WAL vs. MySQL+MyISAM on
write-heavy worksloads
These are real issues, which of course stack on top of things like
outdated opinions from older PG releases with performance issues resolved
in the last few years.
--
* Greg Smith [EMAIL
ce it would remove that as something
separate that needed to be built.
To argue against myself for a second, it may very well be the case that
writing the simpler tool is the only way to get a useful prototype for
building the more complicated one; very easy to get bogged down in feature
creep
sting data. You would thing there would be an organized project
addressing this need around to keep everyone from reinventing that wheel,
but I'm not aware of one.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of
expect it to grow to?", now that's something people can work with.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
ely inappropriate for any environment I work in, because
there really is no thought of security whatsoever in the whole thing.
What I'm still thinking about is whether it's possible to fix that issue
while still keeping the essential simplicity that makes Munin so friendly.
--
that
simple can give dramatically less useful results for predicting PostgreSQL
performance than what you can find out running a real query.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3:
, but I did miss the gigantic and easy to
install Debian software repository.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
ll/upgrade just by playing with the packages that are
different between the two. So someone who installs CentOS now could swap
to RHEL very quickly in a pinch if they have enough cojones to do the
required package substitutions.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltim
isk, there is no way to break the RPM barrier
without hardware support. The fact that he misunderstands such a
fundamental point makes me wonder what other gigantic mistakes might be
buried in his analysis.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
s you've been seeing will make more sense, and you'll be in a
better position to figure out what you should do next:
http://www.westnet.com/~gsmith/content/postgresql/TuningPGWAL.htm
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
uldn't go too high on the max writes per
pass unless you're in a position to run some good tests to confirm you're
not actually making things worse.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
ons aren't finished to my
standards yet, but may be useful anyway so I've posted what I've got so
far.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
e vacuuming parameters is the
more straightforward way to cope with this problem.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
lyze. Once you have a feel for that, add some
indexes back in and see how it degrades. Then you'll know how adding each
one of them impacts your performance. I suspect you're going to have to
redesign your indexing scheme before this is over. I don't think your
current design is
, and that fact that you're satisfied with how nice has
worked successfully for you doesn't have to conflict with an opinion that
it's not the best approach for controlling vacuuming. I just wouldn't
extrapolate your experience too far here.
--
* Greg Smith [EMAIL PROTECTED
ht want to read that goes into more detail than you probably want to
know on this subject if you're like to read more about it--and you really,
really should if you intend to put important data into a PostgreSQL
database.
--
* Greg Smith [EMAIL PROTECTED] http://www.gre
et (too
busy with the real systems that have good controllers). One of these
days...
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appro
very day. Do that for a week, if it's still running your data should be
safe under real conditions.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 7: You can help support the Post
/papers/soft_errors_1_1_secure.pdf
which is a summary of many other people's papers, and quite informative.
I know I had no idea before reading it how much error rates go up with
increasing altitute.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimor
ing effective_cache_size at 5GB or so. That may
require just a bit more upward tweaking of your kernel parameters to
support.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ttings for checkpoint_settings is at the default, that
would be a killer with your workload as well.
That should get you started. If you still aren't happy with performance
after all that, post again with some details about your disk configuration
and an EXPLAIN plan for something that's moving slowl
ing with the WAL parameters like
fsync isn't likely to help here.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
7;s hard to say what else needs to be done. See
http://www.westnet.com/~gsmith/content/postgresql/pg-5minute.htm for more
information on this topic.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
n.html first so
you know what you're playing with, there are some recovery implications
invoved.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will i
get stressed about
making sure you have a good value to set for everything before releasing a
beta, it's a lot easier for others to come in and help fix a couple of
parameters once the basic framework is in place.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
On Mon, 18 Jun 2007, [EMAIL PROTECTED] wrote:
do any of the text-mode browsers implement javascript?
http://links.twibright.com/
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3: Have you
If you're not doing that now, you should consider scripting something up
that does. Going beyond that to having it pick the optimal parameters
more automatically would take AI much stronger than just a genetic
algorithm approach.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Balti
tion about the server.
I wouldn't even bother asking how many CPUs somebody has for what Lance is
building. The kind of optimizations you'd do based on that are just too
complicated to expect a tool to get them right and still be accessible to
a novice.
--
* Greg Smith [EMAIL
navigate that? People
back into a setting for that parameter right now based on memory in their
system, but I never see anybody going "since your main table is X GB
large, and its index is Y GB, you really need enough memory to set
effective_cache_size to Z GB if you want queries/joins on t
out if I'm relieved or really worried to discover that Tom
isn't completely sure what to do with effective_cache_size either.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)-
e day
when I could see this:
$ cat postgresql.conf | grep brain
# - Super-brain Query Optimizer -
sbqo = on # Enables the super-brain
sbqo_reconsider_interval = 5s # How often to update plans
sbqo_brain_size = friggin_huge # Possible values are wee, not_so_wee, and
--
* Greg Smith [
ing operating systems have gotten good enough that tricks like that
are becoming marginal. Pushing more work toward the OS is a completely
viable design choice that strengthens every year.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end o
On Thu, 21 Jun 2007, Scott Marlowe wrote:
And if they've gone to the trouble of implementing RAID-6, they're
usually at least halfway decent controllers.
Unfortunately the existance of the RAID-6 capable Adaptec 2820SA proves
this isn't always the case.
--
* Greg Smith [
ty to get a first generation one that works fairly well before
getting distracted at all by things like this. The people capable of
filling out the intermediate/advanced settings can probably just do a bit
of reading and figure out most of what they should be doing themselves.
--
* Greg Smith [
eference to the parameter documentation
section.
I think that anyone who has been working with the software long to know
what should go into such a section has kind of forgotten about this part
of the documentation by the time they get there. It is an oversight and
yours is an excellent suggesti
arking with as close to
real application data as you can get in order to make good forward
progress.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
etting the most important variables set
to reasonable values. Trying to satisfy every possible user is the path
that leads to a design so complicated that it's unlikely you'll ever get a
finished build done at all.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore,
seful
defaults for those would come out of how the current sample is asking
about read vs. write workloads and expected database size. Those simple
to understand questions might capture enough of the difference between
your two types here.
--
* Greg Smith [EMAIL PROTECTED] http://www.gr
ike
max_fsm_pages and maintenance_work_mem should come out of a different type
of tool that connects to the database.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3: Have you checked our exten
/~gsmith/content/postgresql/pg-5minute.htm for a
quick intro to things to consider.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 6: explain analyze is your friend
10 instead to start), and see if the problem stops happening as
frequently. Your problem looks exactly like a pause at every checkpoint,
and I'm not sure what Richard was thinking when he suggested having them
more often would improve things.
--
* Greg Smith [EMAIL PROTECTED] http://www.gr
h documentation is really spread out, you may find my paper at
http://www.westnet.com/~gsmith/content/linux-pdflush.htm a good place to
start looking into that.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)
ves in the database server storage array, while the PostgreSQL one had
15K RPM ones. A few other small differences as well if you dig into the
configurations, all of which I noted favored the PG system.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Bal
WAL disks that would a fairly short
downtime operation. If you don't reach a wall, the extra drives might
serve as spares to help mitigate concerns about the WAL drives burning out
faster than average because of their high write volume.
--
* Greg Smith [EMAIL PROTECTED] http://www.gr
mergency or for troubleshooting isolation you could always
get any data you needed off any 4-disk set with either controller. The
little 2-disk unit is providing no such redundancy.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(e
re, and don't even bother trying to
separate out the WAL. If you expected hundreds of updates per second,
that's where you need to start thinking about a separate WAL disk, and
even then with 8 disks to spread the load out and a good caching
controller you might still be fine.
--
number and complexity of indexes factor into
things--just add the width of the index in bytes to the size of the
record, or is it worse than that?
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)-
in a way that will degrade performance significantly if you're not very
systematic about testing it many times at various client counts.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 9: I
th/content/postgresql/TuningPGWAL.htm for more
information about this parameter.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
t know how productive speculating about the
cause here will be until there's a test script available so other people
can see where the tipping point is on their system.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(e
vel operations.
[Note: it's possible to run SysBench against a PG database, but the code
is very immature. Last time I tried there were plenty of crashes and
there seemed to be some transaction wrapping issues that caused deadlocks
with some tests.]
--
* Greg Sm
t you're pushing through your disks now. Every dollar spent on
work to quantify that early will easily pay for itself in helping guide
your purchase and future plans; that's what I'd be bringing in people in
right now to do if I were you, if that's not something you'r
back for
the development team for the upcoming 8.3 beta. Probably more productive
use of your time than going crazy trying to fix the issue in 8.2.4.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
r keeps going while checkpoints are being trickled
out, in earlier versions that didn't happen.
The test I'd like to see more people run is to simulate their workloads
with checkpoint_completion_target set to 0.5, 0.7, and 0.9 and see how
each of those settings works relative t
hen you'd
have PGDATA pointing to data/pgsql_data or postgres/pgsql_data which won't
be as confusing.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
than you need but it provides some
pointers to resources to help you better understand how memory management
in Linux works: http://www.westnet.com/~gsmith/content/linux-pdflush.htm
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of bro
to me how to
add manpower to it usefully.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
expensive that it's worth
wandering into an area where your support situation is fuzzy just to save
that money.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3: Have
against
If you're in one of those situations, then perhaps the salesman's claim
could have some merit. There are lots of reasons one might want to use a
SAN, but a higher I/O rate when fairly comparing to connecting disks
directly is unlikely to be on that list.
--
* Greg Smith [E
On Sat, 8 Sep 2007, Joshua D. Drake wrote:
You would have to have lightning handed by God to your server to have a
total power failure without proper shutdown in the above scenario.
Do you live somewhere without thunderstorms? This is a regular event in
this part of the world during the summ
27;re
probably going to need a database-specific benchmark before there's useful
data for your case. Yesterday's meta-coverage at Ars was a nice summary
of the current state of things:
http://arstechnica.com/news.ars/post/20070910-barcelonas-out-and-the-reviews-are-out.html
--
* Gr
rchive or parse the data, but if
I'm watching it I always use dstat now.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 6: explain analyze is your friend
thrown in there is what it
looks like when you don't have enough FSM slots.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
ou've got your background writer configured to
see if it matches situations like this I've seen in the past. The
parameters controlling the all scan are the ones you'd might consider
turning down, definately the percentage and possibly the maxpages as well.
--
* Greg Sm
things improve as that happens may make more sense.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 6: explain analyze is your friend
set of tools for
working the text (presuming you're comfortable with Wiki syntax) that will
get you a pool of reviewers/contributors who can make changes directly
rather than you needing to do all the work yourself.
--
* Greg Smith [EMAIL PROTECTED] http://www.gre
he default.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
d run ipcs when I want
a better idea what's going on. As good of an article on this topic as
I've found is http://gentoo-wiki.com/FAQ_Linux_Memory_Management which
recommends using free to clarify how big the disk cache really is.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmi
suggested at
http://www.westnet.com/~gsmith/content/postgresql/pg-disktesting.htm and
see how your results compare to the single SATA disk example I give there.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast
hem and
you'll see what I mean.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
ct SMART
monitoring here either, which is disappointing, but you can get some
pretty detailed data out of MegaCli so it's not terrible.
I've seen >100MB/s per drive on reads out of small RAID10 arrays, and
cleared 1GB/s on larger ones (all on RHEL5+ext3) with this controller
t without that
basic due diligence, and I'm sure not going to even buy eval hardware
from a vendor that appears evasive about it. There's a reason I don't
personally own any SSD hardware yet.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
g
o squashed in recent years.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.us
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
ght now. Which is
reasonable--that's the context I'm getting more requests to use it in,
just as the filesystem for where the database lives. Those who don't
have a separate volume and filesystem for the db also tend not to care
about filesystem performance differences e
oming as shared_buffers cache size increases for many
workloads, but eventually you can expect to go to far if you try to push
everything in there. Only question is whether that happens at 40%, 60%,
or something higher.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services
1 - 100 of 1007 matches
Mail list logo
