Re: [PATCHES] Optimized pgbench for 8.3

2007-04-06 Thread Tom Lane
Tatsuo Ishii [EMAIL PROTECTED] writes:
 The patches look good to me.

Please commit whatever you think is reasonable.

 BTW, is anybody working on enabling the fill factor to the tables used
 by pgbench? 8.3 will introduce HOT, and I think adding the feature
 will make it easier to test HOT.

I'm not 100% sure that HOT will make it ... but I agree that it'd be
useful for pgbench to support different fillfactor choices.  Please
add if you have time.

regards, tom lane

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


Re: [PATCHES] Optimized pgbench for 8.3

2007-04-06 Thread Tatsuo Ishii
Patch committed. Thanks.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

 The attached is a patch to optimize contrib/pgbench using new 8.3 features.
 
 - Use DROP IF EXISTS to suppress errors for initial loadings.
 - Use a combination of TRUNCATE and COPY to reduce WAL on creating
   the accounts table.
 
 Also, there are some cosmetic changes.
 
 - Change the output of -v option from starting full vacuum...
   to starting vacuum accounts... in reflection of the fact.
 - Shape duplicated error checks into executeStatement().
 
 
 There is a big performance win in COPY with no WAL feature.
 Thanks for the efforts!
 
 Regards,
 ---
 ITAGAKI Takahiro
 NTT Open Source Software Center

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org


Re: [PATCHES] Optimized pgbench for 8.3

2007-04-06 Thread Bruce Momjian

FYI, patch applied by Tatsuo.  Thanks.

---

ITAGAKI Takahiro wrote:
 The attached is a patch to optimize contrib/pgbench using new 8.3 features.
 
 - Use DROP IF EXISTS to suppress errors for initial loadings.
 - Use a combination of TRUNCATE and COPY to reduce WAL on creating
   the accounts table.
 
 Also, there are some cosmetic changes.
 
 - Change the output of -v option from starting full vacuum...
   to starting vacuum accounts... in reflection of the fact.
 - Shape duplicated error checks into executeStatement().
 
 
 There is a big performance win in COPY with no WAL feature.
 Thanks for the efforts!
 
 Regards,
 ---
 ITAGAKI Takahiro
 NTT Open Source Software Center

[ Attachment, skipping... ]

 
 ---(end of broadcast)---
 TIP 5: don't forget to increase your free space map settings

-- 
  Bruce Momjian  [EMAIL PROTECTED]  http://momjian.us
  EnterpriseDB   http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


Re: [PATCHES] Optimized pgbench for 8.3

2007-04-05 Thread Tatsuo Ishii
  Tatsuo, would you please comment on this patch?
 
 Sure. I will come up with a comment by the end of this week.

The patches look good to me.

BTW, is anybody working on enabling the fill factor to the tables used
by pgbench? 8.3 will introduce HOT, and I think adding the feature
will make it easier to test HOT.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

  ---
  
  ITAGAKI Takahiro wrote:
   The attached is a patch to optimize contrib/pgbench using new 8.3 
   features.
   
   - Use DROP IF EXISTS to suppress errors for initial loadings.
   - Use a combination of TRUNCATE and COPY to reduce WAL on creating
 the accounts table.
   
   Also, there are some cosmetic changes.
   
   - Change the output of -v option from starting full vacuum...
 to starting vacuum accounts... in reflection of the fact.
   - Shape duplicated error checks into executeStatement().
   
   
   There is a big performance win in COPY with no WAL feature.
   Thanks for the efforts!
   
   Regards,
   ---
   ITAGAKI Takahiro
   NTT Open Source Software Center
  
  [ Attachment, skipping... ]
  
   
   ---(end of broadcast)---
   TIP 5: don't forget to increase your free space map settings
  
  -- 
Bruce Momjian  [EMAIL PROTECTED]  http://momjian.us
EnterpriseDB   http://www.enterprisedb.com
  
+ If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org


Re: [PATCHES] Optimized pgbench for 8.3

2007-04-04 Thread Tatsuo Ishii
 Tatsuo, would you please comment on this patch?

Sure. I will come up with a comment by the end of this week.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

 ---
 
 ITAGAKI Takahiro wrote:
  The attached is a patch to optimize contrib/pgbench using new 8.3 features.
  
  - Use DROP IF EXISTS to suppress errors for initial loadings.
  - Use a combination of TRUNCATE and COPY to reduce WAL on creating
the accounts table.
  
  Also, there are some cosmetic changes.
  
  - Change the output of -v option from starting full vacuum...
to starting vacuum accounts... in reflection of the fact.
  - Shape duplicated error checks into executeStatement().
  
  
  There is a big performance win in COPY with no WAL feature.
  Thanks for the efforts!
  
  Regards,
  ---
  ITAGAKI Takahiro
  NTT Open Source Software Center
 
 [ Attachment, skipping... ]
 
  
  ---(end of broadcast)---
  TIP 5: don't forget to increase your free space map settings
 
 -- 
   Bruce Momjian  [EMAIL PROTECTED]  http://momjian.us
   EnterpriseDB   http://www.enterprisedb.com
 
   + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [PATCHES] Optimized pgbench for 8.3

2007-03-24 Thread Bruce Momjian

Your patch has been added to the PostgreSQL unapplied patches list at:

http://momjian.postgresql.org/cgi-bin/pgpatches

It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.

---


ITAGAKI Takahiro wrote:
 The attached is a patch to optimize contrib/pgbench using new 8.3 features.
 
 - Use DROP IF EXISTS to suppress errors for initial loadings.
 - Use a combination of TRUNCATE and COPY to reduce WAL on creating
   the accounts table.
 
 Also, there are some cosmetic changes.
 
 - Change the output of -v option from starting full vacuum...
   to starting vacuum accounts... in reflection of the fact.
 - Shape duplicated error checks into executeStatement().
 
 
 There is a big performance win in COPY with no WAL feature.
 Thanks for the efforts!
 
 Regards,
 ---
 ITAGAKI Takahiro
 NTT Open Source Software Center

[ Attachment, skipping... ]

 
 ---(end of broadcast)---
 TIP 5: don't forget to increase your free space map settings

-- 
  Bruce Momjian  [EMAIL PROTECTED]  http://momjian.us
  EnterpriseDB   http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly