pretty big penalty but debug isn't nearly as bad.
Joshua D. Drake
I'd want to see benchmarking on a couple of platforms to
> prove that it doesn't slow things down before making such a change.
>
> --
> * Greg Smith [EMAIL PROTECTED] http://www.gregsmith.
ated that he is o.k. with removing the offending
code. Instead of flogging him, how about we just remove the code and
mark it up for over zealousness.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7
f this, I took our PITR backup and
> restored it properly, and everything seems to be functioning
> correctly from my tests.
x86_64 is x86_64, regardless of intel or amd.
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Em
who wants first bite and what do they
want :)
Sincerely,
Joshua D. Drake
P.S. It is RHEL 5.
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com
itself. :). But please
> let me know your comments on why you feel this is useless.
> But i guess(I may be wrong), you may be wrong about the grammar
> support part.
Wow, you are new here aren't you? I assure you, Tom is the last person
that is going to be wrong about grammar supp
what is the real difference
between 28 spindles with RAID 5 versus 10?
> installation would be a management nightmare. Also, with personal
> installations, nobody need have root privileges, which just seems
> like a real good idea.
No question.
Joshua D. Drak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 02 Nov 2007 17:11:30 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > Tom Lane <[EMAIL PROTECTED]> wrote:
> >> Yeah, I'd vote for people just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 04 Nov 2007 19:28:46 +0100
Zdenek Kotala <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
>
> >
> > x86_64 is x86_64, regardless of intel or amd.
>
> Not exactly, ask kernel guys ;-). But for user spac
n/pgpatches
>
It would be great if this would push to the wiki. That has been working
really well through the cycle.
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 05 Nov 2007 18:57:39 +
Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>
> > On Mon, 5 Nov 2007 12:47:10 -0500 (EST)
> > Bruce Momjian <[EMAIL PROTECTED
ssues on some isolated workloads on
> in-memory databases, as well as WAL writing. I'll generate the data
> directly on the system.
>
> Any chance we can validate the I/O config and publish bonnie results
> first, please?
I don't see why not.
Sincerely,
Joshua D. Drake
"duh" department to ignore. A set
of SQL functions would certainly be appropriate here.
Sincerely,
Joshua D. Drake
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
quire extremely expensive hardware to do so.
Joshua D. Drake
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
: If you want to extend
its size, you have to stop the database instance -- which is not
considered good.
Well, depending on the size you could push the table to another table
space, drop the old table space, resize the ramfs, and reverse the
previous :)
Joshua D. Drake
Regards
the OP.
Cost is always an issue, even if implicit. If the person is so hung up
on the idea of pushing things into ram there is a pretty good
possibility they have priced out the 50 and 100 spindle devices needed
to get the same type of performance.
Sincerely,
Joshua D. Drake
cheers
ntel.com/performance/server/xeon/intspd.htm
http://www.intel.com/performance/server/xeon/fpspeed.htm
Sincerely,
Joshua D. Drake
---(end of broadcast)---
TIP 6: explain analyze is your friend
Gregory Maxwell wrote:
On Nov 14, 2007 10:12 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
http://www.intel.com/performance/server/xeon/intspd.htm
http://www.intel.com/performance/server/xeon/fpspeed.htm
That says precisely nothing about the matter at hand. Someone should
simply cha
erhaps 72), but we have a couple of violations either way, which I'd
> like to fix, but what to?
Why not just have the terminal control the wrap? It isn't just \? that
does it.
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Sup
width, but if you try to print in the
> last column you may get unexpected extra blank lines.
O.k. this might be offtopic if it is feel free to smack me... but I
have noticed that psql really breaks on terminals that are wide.. \df
works fine, but \df+ is completely broke.
Can't we just ask the term
t to be coordinated so that what is in the release doesn't
vary depending on who committed last.
O.k., so what do you want to do? Or more to the point, is there
something I can help with? I have machines with 2.59... Marc do you have
any left with 2.59?
Sincerely,
Joshua D. Drake
ersion...
Sincerely,
Joshua D. Drake
- --On Thursday, November 15, 2007 23:37:22 -0500 Tom Lane <[EMAIL PROTECTED]>
wrote:
[EMAIL PROTECTED] (Marc G. Fournier) writes:
configure (r1.570 -> r1.571)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/configure?r1=1.570
Marc G. Fournier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Thursday, November 15, 2007 20:49:04 -0800 "Joshua D. Drake"
<[EMAIL PROTECTED]> wrote:
Marc G. Fournier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
'k, 2.59 isn't even
idea of a "freeze" :). E.g; All animals must go
green and stay green with zero additional commits for 24 hours before
we wrap.
Is that something that sounds reasonable?
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
> ---(en
g an older version of autoconf? I mean, if everything is put
together with 2.61, are 2.59 versions going to have an issue?
Joshua D. Drake
-
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTEC
is currently accepted. That way we don't have to make that distinction.
Autoconf 2.59 is going to be predominantly in the wild (rhel 5, centos5
, dapper, debian) for at least another 3-4 years.
Joshua D. Drake
regards, tom lane
---(end of br
l semantic gap
> there.
Perhaps but the practical gap is much narrower.
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
> ---(end of
> broadcast)--- TIP 2: Don't 'kill -9' the
> postm
eplace('2343'::money::text, '[^$,]*',
> '', 'g')::numeric; regexp_replace
>
> 2343.00
> (1 row)
>
> but the '$' and ',' are locale-specific and I can't think of a way to
> do t
formance:
HOT -- has a direct correlation to performance because without it
we vacuum more. Not only more, but in a lot of cases it resolves a
serious PostgreSQL limitation for high velocity tables.
Phantom Xid - less vacuuming
The sequential scan thing Jeff Davis did
The reduced size of the tup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 27 Nov 2007 18:18:52 +
Simon Riggs <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-11-27 at 10:08 -0800, Joshua D. Drake wrote:
> > Simon Riggs <[EMAIL PROTECTED]> wrote:
> Agreed. I either initiated or assisted with
STABLE
> branch since 7.3.20. Rather than just leaving those to rot, maybe the
> actual policy should be "only one more update after 8.3 comes out".
>
> Comments, opinions?
Release 7.3.21 with and EOL addendum :). E.g; this is the last release
of 7.3 and
re these
> are at. One is likely to be running RHEL, one Solaris.
The RHEL one as I know it, is the MyYearbook donated one. We are
currently unaware of the status of that machine except to say it is
currently running Gentoo.
I don't know the status of the Solaris machine except that I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 27 Nov 2007 21:00:03 +
Simon Riggs <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-11-27 at 12:36 -0800, Joshua D. Drake wrote:
>
> > The RHEL one as I know it, is the MyYearbook donated one. We are
> > currently unawa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 27 Nov 2007 21:00:03 +
Simon Riggs <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-11-27 at 12:36 -0800, Joshua D. Drake wrote:
>
> > The RHEL one as I know it, is the MyYearbook donated one. We are
> > currently unawa
om the release notes (btw, if
> people have countries for the folks who aren't attributed, I'd
> appreciate them). Of course, there are many contributors to essential
> non-core code who should be listed as well:
It would be useful to know the requirements to be listed...
Joshua
s of different test from
pgbench, odbcbench, dbt2, custom scripts etc... to provide trending for
a particular host. That way if one host does 50tps continuously and
then changes one way or the other, there is at least a flag...
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Compa
bvious the only question is it only
committers to the source tree or do we want to give equal billing to
the -www guys (I think yes to equal billing)
Members (really I think this should be contributors but then it is
duplicative)
Hacker Emeritus
Special Thanks (not sure about thi
ld all support the new protocol.
Except that we just broke the proposed upgrade path if we do that...
Let's not put people in a catch-22.
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Pos
> Sorry, forgot to say what to put instead. I'll go with "Canada" --
> it's more exotic :)
I believe the list is where you are actually at. Aren't you in the UK
right now?
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Sup
web/infrastructure team.
Define Hacker. And I could argue that some are members of PGDG. What
about those who provide just as much time and energy in advocacy as
others do on -heackers? What about people that are working on external
projects only such as Slony or PLproxy?
Sincerely,
Joshua D. Drake
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 16:53:43 +
Dave Page <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> > On Wed, 28 Nov 2007 16:27:42 +
> > Dave Page <[EMAIL PROTECTED]> wrote:
> >
> >> Why not Hackers? Noon
nough but I think the point is still relevant, in that we really
don't want to state specifically what a "Major" contributor is, I think
it opens us up to more bad mojo than just saying you are either a
regular contributor, or not :)
Sincerely,
Joshua D. Drake
- --
=== The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 13:15:52 -0500
Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
>
> Joshua D. Drake wrote:
> >Committers <-- this is obvious the only question is it only
> > committers to the source tree or do we
ling list subscribers :). However a reasonably managed
list that shows strength in not only numbers but a solid base of
frequent contributors, show duration and maturity within the project.
Sincerely,
Joshua D. Drake
>
> -Kevin
>
>
>
>
> ---
ointing to a logistical problem with that thought
process. You are a hacker, you are also a pgfoundry admin and buildfarm
maintainer...
Which list would you like to be under?
Joshua D. Drake
P.S. I know that answer, that isn't the point.
- --
=== The PostgreSQL Company: Command Promp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 15:06:58 -0400
"Marc G. Fournier" <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> - --On Wednesday, November 28, 2007 08:20:04 -0800 "Joshua
akes sense, based on that to break it out.
However there is another consideration in that at least two core
members seem to have zero interest in being involved in a very public
way like you suggest above. So perhaps it makes sense for core to be
inclusive of the list and instead push all "contacts
sidering we still have Postgres95 in the tree I would bet you are
right :)
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
nother beta before RC1 would be warranted.
I think the email is not quite clear :). There is a Beta 4 coming, the
problem is packagers aren't really available this week so if it comes
it will be next week.
At least that is last I heard.
Joshua D. Drake
>
> -Neil
&
column being updated isn't indexed?
Seems kind of long but isn't that "exactly" what it does?
Sincerely,
Joshua D. Drake
>
> cheers
>
> andrew
>
> ---(end of
> broadcast)--- TIP 1: if posting/reading
>
about? :)
Stealth marketing :)...
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to
eed to be mentioning contributions like that. Those
who have contributed are in the logs.
Further those who have provided reasonable contribution really should be
mentioned on the contributors page that is up for discussion which would
make the rest of this moot yes?
Sincerely,
Joshua
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
...Further those who have provided reasonable contribution really should be
mentioned on the contributors page that is up for discussion which would
make the rest of this moot yes?
I don't have any objection
I improve something adding some missing option/command to the above steps?
Where and how to apply the TRACE_SORT option?
Any other useful options?
You don't want --enable-cassert on a production machine it is a
performance hit.
Joshua D. Drake
---(e
le mot juste. Best I could do was "spread
> checkpoint" or "time-extended checkpoint". Anybody have a better
> idea?
balanced
gradual
extended (I see you mention time-extended but wouldn't time be implicit
based on the actual docs and thus we only need extended
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 6 Dec 2007 19:43:29 -0800
David Fetter <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 06, 2007 at 07:19:44PM -0800, Joshua D. Drake wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Thu, 0
espond especially fast.
If the community-at-large can't handle a bug, we certainly have enough
institutional memory to try to contact the original author, even if that
address isn't in the SGML docs.
Perhaps the at a minimum the email goes in the commit?
Joshua D. Drake
a handful of
built-in data types but I suppose there will always be holes in this area
anyways.
What are we gaining here? A 32bit postmaster can't start a 64bit one...
Running select version() will tell you if you are running 64 or 32bit...
What am I missing?
Josh
actually do the work
> required to list _all_ fixes/changes in a release. The job isn't that
> hard, maybe a few days work for someone experienced.
O.k. I would buy this..
Joshua D. Drake
>
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
between a individual who is a contributor and a company that
is a contributor interesting.
Sincerely,
Joshua D. Drake
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
lopers
list) as the definitive source and just provide a link.
Sincerely,
Joshua D. Drake
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
see us
going back to -u regardless of how logical it may be.
Joshua D. Drake
---(end of broadcast)---
TIP 6: explain analyze is your friend
Gregory Stark wrote:
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
Joshua D. Drake wrote:
Note that I am not arguing one way or the other, but I find the
distinction between a individual who is a contributor and a company that
is a contributor interesting.
Individual mention
Bruce Momjian wrote:
Joshua D. Drake wrote:
However as a user I find it helpful to get a kind of overview of the kinds of
invisible changes there were so I can get a feel for the magnitude of the
improvements between versions.
I agree with this as well. However, I am starting to wonder if the
Bruce Momjian wrote:
Joshua D. Drake wrote:
I assumed the white paper would have proper attribution.
Right, but is the white paper going to be thorough to mention _all_
changes?
Hmmm good question which gets back to where we started :). My very first
thought on all of this was that we
cific circumstances that a
password prompt would not appear. Thus we added the option for -W.
Sincerely,
Joshua D. Drake
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
Bruce Momjian wrote:
Joshua D. Drake wrote:
Bruce Momjian wrote:
Joshua D. Drake wrote:
I assumed the white paper would have proper attribution.
Right, but is the white paper going to be thorough to mention _all_
changes?
Hmmm good question which gets back to where we started :). My very
ers, two a relatively new.
Full names makes the most sense.
Sincerely,
Joshua D. Drake
cheers
andrew
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 10 Dec 2007 12:14:58 -0500 (EST)
Kris Jurka <[EMAIL PROTECTED]> wrote:
>
>
> On Mon, 10 Dec 2007, Joshua D. Drake wrote:
>
> > 3. It was grunt work that should have been done with the original
> > patch that
nce we have two Heikkis it will
be obvious to anyone that we are the World's most globally developed
advanced Open Source database.
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 10 Dec 2007 18:13:58 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Alvaro Herrera wrote:
> > Joshua D. Drake wrote:
> >
> > > We even have two Gavins. However I think we will truly reach the
> > &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 10 Dec 2007 17:16:12 -0500 (EST)
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Kris Jurka wrote:
> >
> >
> > On Mon, 10 Dec 2007, Joshua D. Drake wrote:
> >
> > > 3. It was grunt work that should ha
our system of feedback works (good), but the
> criteria used isn't 100% agreed.
>
> My point is that it isn't that I am too subjective and closed to
> feedback on adding/removing items, but rather the policy used isn't
> open for feedback; but it really is. Should we o
pent more than a day.
That's fair. There is a psql section in the release notes. Why not just
add it there.
Various psql improvements including \d commands for tsearch, \prompt
capability, and better \timing functionality. (Andrew Dunstan,
Stefan Kaltenbrunner, Tom Lane, Chad Wagner)
Sincere
clear policy. There is clear policy to you and Tom but I have
been here a lot of years and didn't know about it.
If that is the policy, fine :) but it needs to get documented somewhere
that is no buried in a list archive that gets thousands of messages a
month.
Sincerely,
Joshua D. Drake
-
lying
issue though. Did you see my email to Tom on the matter? About grouping?
Sincerely,
Joshua D. Drake
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTE
test
---(end of broadcast)---
TIP 6: explain analyze is your friend
global indexes are bad for certain situations for others they are
required. Constraint Exclusion/Partitioning is not only for ginormous
tables.
It can also be used for maintenance efficiency, micro optimizations and
just general data architecture.
Joshua D. Drake
- --
The PostgreSQL Comp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Greenplum as well as other Real Life stuff.
For those of us here who have no idea what you are talking about can
you define what "Real Life" is like?
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.comm
s which perform this automatically will not need
> changing.
>
> We can keep the message in case something removes the directory later.
>
> Views?
+1
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1
it
for 6 months?
Is a translator really not able to change 3 words in a week? Come again.
I think it is likely more about being able to reach the translators. The
more common ones such as yourself are obvious but others may not be.
Either way, I think that the change is valid and we need t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 13 Dec 2007 11:12:26 -0800
"Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
> > > Hmm --- I was testing a straight crash-recovery scenario, not
> > > restoring from archive. Are you sure your restore_command sc
> >> somewhere, so companies could evaluate it.
> >>
> >
> > A page on the developer wiki makes sense to me...
>
> The question is how it's visible to companies ?
This really doesn't belong on -hackers... :).
Can we move it to -www?
Sincerely,
Josh
I know that CMD would participate and although I am being presumptuous
I pretty sure EDB is also a no brainer.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Dona
Tom very seriously.
Andrew is absolutely correct here. If you do not agree with Tom, you
best prove why. Otherwise your patch will likely be ignored on
submission.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564
ve them different databases."
I think there is a fundamental disconnect here. The "Give them
different databases" argument is essentially useless. Consider a
organization that has Sales and HR.
You don't give both a separate database. They need access to "some" of
Andrew Dunstan wrote:
It might well be useful for us to look at drafting an SELinux policy,
even if it's not universal. After all, this situation is precisely the
sort of thing that SELinux is about, ISTM.
http://code.google.com/p/sepgsql/
???
Sincerely,
Joshua D.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 29 Dec 2007 14:40:29 -0500 (EST)
Greg Smith <[EMAIL PROTECTED]> wrote:
> On Sat, 29 Dec 2007, Joshua D. Drake wrote:
>
> > http://code.google.com/p/sepgsql/
> > ???
>
> Getting that to work required some o
he PostgreSQL Day is planned. I am working with John Mark to also
have a PostgreSQL Day at LinuxWorld as well.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Donate to the Post
query:
SELECT relname, age(relfrozenxid) FROM pg_class WHERE relkind = 'r';
To:
SELECT relname, age(relfrozenxid) FROM pg_class WHERE relkind = 'r' OR
relkind = 't';
I apologize if this doesn't quite make sense. I am very tired but I
wanted to make sure to g
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I spent the better part of this evening tracking down a problem with a
high velocity database. The database had entered the point of no return
by invoking xidStopLimit.
8.2.4
Joshua D. Drake
Joshua D. Drake wrote:
Ping?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I spent the better part of this evening tracking down a problem with a
high velocity database. The database had entered the point of no return
by invoking xidStopLimit.
This by itself isn't a problem be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 7 Jan 2008 09:18:24 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
>
> >> SELECT oid::regclass FROM pg_class WHERE
> >> reltoastrelid='pg_toast.pg_toast_49013869
e of differences.
1. I had to manually vacuum because we had already hid xidStoplimit.
2. Postgres has been restarted multiple times and it made zero
difference.
E.g; PostgreSQL isn't cleaning up after itself and it isn't apparent
when it happens.
Sincerely,
Joshua D.
historical leftover? If it is
> only needed for emergency, should it not have a different name?
> Just curious..
There are times when it is required, usually when people don't
configure normal vacuum/autovacuum correctly.
Sincerely,
Joshua D. Drake
>
> Holger
>
>
l time to resolution, and not requiring hacking the backend
> to get there.
>
+1
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Donate to the PostgreSQL Project: http://www.p
release when
it is done not release because lots of people are waiting for it.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Donate to the PostgreSQL Project: http://www.postgresql.
ariable into the mix. This machine was a PITR
slave that was pushed into production about two weeks ago.
Joshua D. Drake
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
with_dates.html
and:
http://www.databasejournal.com/features/mssql/article.php/3456991
Or worlds above us in usability.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Dona
re to use the plain text
backup.
I think his email was very well written and a simple request of
discussion of alternatives as well as future plans.
Sincerely,
Joshua D. Drake
> Cheers,
> mark
>
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support:
one of
those "University Places"? From people outside the Computer Science
department? Maybe even some people in Industrial Psychology? Somebody
probably needs a Master's project
Actually you just need to not be on -hackers :). This belongs over in
1101 - 1200 of 2966 matches
Mail list logo
