Simon Riggs escribió:
> On Fri, 2007-03-02 at 18:37 -0300, Alvaro Herrera wrote:
> > Bruce Momjian escribió:
> > > Simon Riggs wrote:
> > > > CLUSTER does not need changes for HOT, as things stand currently, mainly
> > > > because its MVCC behaviour is broken.
> > > --
On Fri, 2007-03-02 at 18:37 -0300, Alvaro Herrera wrote:
> Bruce Momjian escribió:
> > Simon Riggs wrote:
> > > CLUSTER does not need changes for HOT, as things stand currently, mainly
> > > because its MVCC behaviour is broken.
> >
> >
> > That's oddly disco
Bruce Momjian escribió:
> Simon Riggs wrote:
> > On Thu, 2007-03-01 at 22:35 +0530, Pavan Deolasee wrote:
> > > Merlin Moncure wrote:
> > > > On 3/1/07, Pavan Deolasee <[EMAIL PROTECTED]> wrote:
> > > >>
> > > > seems pretty solid except for one possible problem...at one point when
> > > > I dr
Tatsuo Ishii wrote:
> Just for curiosity, I would like to ask you why you need to modify
> pgbench. pgbench can accept custom SQL scripts...
>
> P.S. HOT seems to be one of the greatest enhancements since PostgreSQL
> was born!
Yep, I share your enthusiasm.
--
Bruce Momjian <[EMAIL PROTECTED
Pavan Deolasee wrote:
> Zeugswetter Andreas ADI SD wrote:
> >>> accounts 157895 (initial size) 49284 (increase)
> >>> accounts_pkey 19709 (initial size) 19705 (increase)
> >>>
> >>>
> >> Just to clarify, the relation size and increase is in number
> >> of blocks.
> >
> > The n
Simon Riggs wrote:
> On Thu, 2007-03-01 at 22:35 +0530, Pavan Deolasee wrote:
> > Merlin Moncure wrote:
> > > On 3/1/07, Pavan Deolasee <[EMAIL PROTECTED]> wrote:
> > >>
> > > seems pretty solid except for one possible problem...at one point when
> > > I dropped then later added the index on 'a
On 3/2/07, Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
Just for curiosity, I would like to ask you why you need to modify
pgbench. pgbench can accept custom SQL scripts...
Oh yes, there was no real need to modify pgbench.
Thanks,
Pavan
--
EnterpriseDB http://www.enterprisedb.com
Just for curiosity, I would like to ask you why you need to modify
pgbench. pgbench can accept custom SQL scripts...
P.S. HOT seems to be one of the greatest enhancements since PostgreSQL
was born!
--
Tatsuo Ishii
SRA OSS, Inc. Japan
> Hi All,
>
> Here are some preliminary numbers with the HOT 4
Zeugswetter Andreas ADI SD wrote:
accounts 157895 (initial size) 49284 (increase)
accounts_pkey 19709 (initial size) 19705 (increase)
Just to clarify, the relation size and increase is in number
of blocks.
The numbers are quite impressive :-) Have you removed the select
On Thu, 2007-03-01 at 22:35 +0530, Pavan Deolasee wrote:
> Merlin Moncure wrote:
> > On 3/1/07, Pavan Deolasee <[EMAIL PROTECTED]> wrote:
> >>
> > seems pretty solid except for one possible problem...at one point when
> > I dropped then later added the index on 'abalance', I got spammed
> > 'W
Merlin Moncure wrote:
> On 3/1/07, Pavan Deolasee <[EMAIL PROTECTED]> wrote:
>>
> seems pretty solid except for one possible problem...at one point when
> I dropped then later added the index on 'abalance', I got spammed
> 'WARNING: found a HOT-updated tuple' from psql prompt.
Thats intentional.
On 3/1/07, Pavan Deolasee <[EMAIL PROTECTED]> wrote:
Hi All,
Here are some preliminary numbers with the HOT 4.0 patch that I sent
out earlier today. These are only indicative results and should not be
used to judge the performance of HOT in general. I have intentionally
used the setup favorabl
> > accounts 157895 (initial size) 49284 (increase)
> > accounts_pkey 19709 (initial size) 19705 (increase)
> >
> >
> Just to clarify, the relation size and increase is in number
> of blocks.
The numbers are quite impressive :-) Have you removed the selects on
accounts too
On 3/1/07, Pavan Deolasee <[EMAIL PROTECTED]> wrote:
accounts 157895 (initial size) 49284 (increase)
accounts_pkey 19709 (initial size) 19705 (increase)
Just to clarify, the relation size and increase is in number of blocks.
Thanks,
Pavan
--
EnterpriseDB http://w
Hi All,
Here are some preliminary numbers with the HOT 4.0 patch that I sent
out earlier today. These are only indicative results and should not be
used to judge the performance of HOT in general. I have intentionally
used the setup favorable to HOT. The goal here is to point out the best
usage
15 matches
Mail list logo