"Greg Smith" <[EMAIL PROTECTED]> writes:
> On Wed, 25 Jul 2007, Gregory Stark wrote:
>
>> Does gentoo these days have binary packages? source packages do implicitly
>> require custom builds...
>
> You can install with binaries now so it doesn't take forever to get started,
> but the minute you're
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I propose applying this patch from 8.1 onwards. HEAD would get an
> additional treatment to avoid the balancing problem.
If you're going to insert an early unlock, it should be as early as
possible, ie right after the RelationTruncate() call. The book
Oleg Bartunov wrote:
> On Wed, 25 Jul 2007, Erikjan wrote:
>
> > In
> > http://momjian.us/expire/fulltext/HTML/textsearch-intro.html#TEXTSEARCH-DOCUMENT
> >
> > it says:
> >
> > "A document is any text file that can be opened, read, and modified."
>
> OOps, in my original documentation it was:
>
Oleg Bartunov wrote:
> >> Second, I can't figure out how to reference a non-default
> >> configuration.
> >
> > See the multi-argument versions of to_tsvector etc.
> >
> > I do see a problem with having to_tsvector(config, text) plus
> > to_tsvector(text) where the latter implicitly references a co
"Simon Riggs" <[EMAIL PROTECTED]> wrote:
> Read the heap blocks in sequence, but make a conditional lock for
> cleanup on each block. If we don't get it, sleep, then try again when we
> wake up. If we fail the second time, just skip the block completely.
When we allow some skips in removing dead
Dave Page <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> So maybe the *real* question to ask is why we have separate GUCs for
>> stats_row_level and stats_block_level. Shouldn't we fold them into a
>> single switch? It's hard to see what having just one of them turned on
>> will save.
> Any re
I wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
>> Anybody got any objection to setting it on by default?
> Yes. It's pure overhead with no redeeming social value except to those
> who actually want to look at that sort of stat, and those who do can
> certainly turn it on for themselves.
On
Oleg Bartunov wrote:
> Bruce,
>
> I sent you link to my wiki page with summary of changes
> http://www.sai.msu.su/~megera/wiki/ts_changes
>
> Your documentation looks rather old.
I have updated it to reflect your changes:
http://momjian.us/expire/fulltext/HTML/textsearch-tables.html
--
Why is stats_block_level = off by default?
Is there a measurable cost to enabling this? We already have
stats_row_level = on, so presumably the overhead of setting
stats_block_level to on cannot be any worse than that.
Anybody got any objection to setting it on by default?
--
Simon Riggs
En
On Thu, 26 Jul 2007, Joshua D. Drake wrote:
IMO, a multiboot is o.k. but a vm isn't worth it. This box is big enough to
actually starting looking at SMP and I/O issues for PostgreSQL that we
normally can't because we don't have access to the hardware in the community.
Certainly agree with tha
I've been thinking some more about scalability and what we need to
measure in order to locate and remove the next set of bottlenecks.
EXCLUSIVE LOCKS
The lock wait time distribution and the sum of lock held time is of
interest in understanding contention.
SHARED LOCKS
Shared locks present some
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
> Personally, I think CentOS 5 is probably the most reasonable choice. It is
> what (or RHEL 5 which is the same) a good portion of our community is going
> to be running. It is also easy to work with.
>
> Another alternative would be Debian or Ubuntu
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Really there's a pretty good argument for having several different OS'es
available on the box --- I wonder whether Gavin is up to managing some
sort of VM or multiboot setup.
IMO, a multiboot is o.k. but a vm isn't
Tom Lane wrote:
Greg Smith <[EMAIL PROTECTED]> writes:
Really there's a pretty good argument for having several different OS'es
available on the box --- I wonder whether Gavin is up to managing some
sort of VM or multiboot setup.
IMO, a multiboot is o.k. but a vm isn't worth it. This box is
Greg Smith <[EMAIL PROTECTED]> writes:
> But this is pushing forward PostgreSQL development you're doing here. If
> you've got a problem such that something works differently based on the
> order in which you built the packages, which is going to be unique to
> every Linux distribution already,
Alvaro Herrera wrote:
> Tom Lane wrote:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > What I'm requesting here is that the sleep in count_nondeletable_pages()
> > > be removed and that change backpatched to 8.2 and 8.1.
> >
> > Are you sure that that is, and always will be, the only sleep i
Tom Lane wrote:
> So maybe the *real* question to ask is why we have separate GUCs for
> stats_row_level and stats_block_level. Shouldn't we fold them into a
> single switch? It's hard to see what having just one of them turned on
> will save.
Any reason not to just fold them both into stats_st
Just wanted to record a quick idea in case its useful in the future.
VACUUM reads all blocks in sequence and waits on each one to acquire a
cleanup lock.
If VACUUM is running with vacuum_delay enabled then we might take a
slightly different approach:
Read the heap blocks in sequence, but make a
Let me look at what makes sense there, I am open to it.
On 7/26/07, Tom Lane <[EMAIL PROTECTED]> wrote:
Greg Smith <[EMAIL PROTECTED]> writes:
> But this is pushing forward PostgreSQL development you're doing here. If
> you've got a problem such that something works differently based on the
> o
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Really there's a pretty good argument for having several different OS'es
>> available on the box --- I wonder whether Gavin is up to managing some
>> sort of VM or multiboot setup.
> IMO, a multiboot is o.k. but a vm isn't worth it
I've been looking at the way that the async-commit patch conserves
shared memory space by remembering async commit LSNs for groups of
transactions on a clog page, rather than having an LSN for each
individual transaction slot. This seems like a good plan to me,
but I'm confused about one point. T
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> Anybody got any objection to setting it on by default?
Yes. It's pure overhead with no redeeming social value except to those
who actually want to look at that sort of stat, and those who do can
certainly turn it on for themselves.
On Thu, 26 Jul 2007, Gregory Stark wrote:
So for me to reproduce your [Gentoo] environment you would have to send
me the complete history of what packages you installed. I would have to
reproduce the entire history including installing and building
intermediate versions.
If one's goal is to
Greetings,
In working on the minor patch to COPY CSV mode tonight, I ran into a
problem with the utf8 conversion build process in CSV and was just
wondering if there's something wacky on my system or if other people
have seen this:
[EMAIL PROTECTED]:.../pgsql.build> ../pgsql/configure
Satoshi Nagayasu <[EMAIL PROTECTED]> writes:
> I think the stats stuff should be on by default even if it causes
> some performance penalty.
> Because when we have performance problems on the production system,
> it needs more performance penalty (about 5%~) to measure the stats
> by turning their
* Stephen Frost ([EMAIL PROTECTED]) wrote:
> I did a 'cvs -z3 up' prior to this, and most things seemed to be
So, of course, in re-reading this I think to myself "wait, this guy
should be using 'cvs -z3 up -dP'", and while I havn't tested it yet, the
directories showed up, so I'm thinking proble
Tom Lane wrote:
> I wrote:
> > "Simon Riggs" <[EMAIL PROTECTED]> writes:
> >> Anybody got any objection to setting it on by default?
>
> > Yes. It's pure overhead with no redeeming social value except to those
> > who actually want to look at that sort of stat, and those who do can
> > certainly
Tom,
>> Yes. It's pure overhead with no redeeming social value except to those
>> who actually want to look at that sort of stat, and those who do can
>> certainly turn it on for themselves.
I think the stats stuff should be on by default even if it causes
some performance penalty.
Because when
On Thu, 26 Jul 2007, Bruce Momjian wrote:
Oleg Bartunov wrote:
Bruce,
I sent you link to my wiki page with summary of changes
http://www.sai.msu.su/~megera/wiki/ts_changes
Your documentation looks rather old.
I have updated it to reflect your changes:
http://momjian.us/expire/fullt
On Thu, 26 Jul 2007, Bruce Momjian wrote:
Oleg Bartunov wrote:
On Wed, 25 Jul 2007, Erikjan wrote:
In
http://momjian.us/expire/fulltext/HTML/textsearch-intro.html#TEXTSEARCH-DOCUMENT
it says:
"A document is any text file that can be opened, read, and modified."
OOps, in my original docume
>
> 1) Document the problem and do nothing else.
> 2) Make default_text_search_config a postgresql.conf-only
>setting, thereby making it impossible to change by non-super
>users, or make it a super-user-only setting.
> 3) Remove default_text_search_co
On Fri, 27 Jul 2007, Pavel Stehule wrote:
1) Document the problem and do nothing else.
2) Make default_text_search_config a postgresql.conf-only
setting, thereby making it impossible to change by non-super
users, or make it a super-user-only setting.
32 matches
Mail list logo
