Re: [PERFORM] Postgres batch write very slow - what to do

On 3/13/07, femski <[EMAIL PROTECTED]> wrote: I have a batch application that writes approx. 4 million rows into a narrow table. I am using JDBC addBatch/ExecuteBatch with auto commit turned off. Batch size is 100. So far I am seeing Postgres take roughly five times the time it takes to do this i

Re: [PERFORM] PostgreSQL 8.2.3 VACUUM Timings/Performance

Hi All, Okay, I'm getting a little further now. I'm about to create entries in the pg_autovacuum system tables. However, I'm a little confused as to how I go about finding out the OID value of the tables. The pg_autovacuum table requires the OID of the table you want to create settings for (vac

Re: [PERFORM] Postgres batch write very slow - what to do

Carlos Moreno wrote: > Joshua D. Drake wrote: > >> insert into foo(bar) values (bang) (bong) (bing) ...? >> >> >> > > Nit pick (with a "correct me if I'm wrong" disclaimer :-)) : > > Wouldn't that be (bang), (bong), (bing) ?? Yes. J > > Carlos > -- > > > ---

Re: [PERFORM] Postgres batch write very slow - what to do

Joshua D. Drake wrote: insert into foo(bar) values (bang) (bong) (bing) ...? Nit pick (with a "correct me if I'm wrong" disclaimer :-)) : Wouldn't that be (bang), (bong), (bing) ?? Carlos -- ---(end of broadcast)--- TIP 2: Don't '

[PERFORM] unsubscribe

---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [PERFORM] Determine dead tuples size

Alexey Romanchuk <[EMAIL PROTECTED]> writes: > When i try to sum all size (live, dead and free) the sum is not equal > total size. For this table 206555428 + 3380295 + 13896816 = 223832539. > The difference between total and sum is 9410085. It is near 5%. pgstattuple is a bit simplistic: it doesn'

Re: [PERFORM] Postgres batch write very slow - what to do

femski wrote: > Folks ! > > I have a batch application that writes approx. 4 million rows into a narrow > table. I am using JDBC addBatch/ExecuteBatch with auto commit turned off. > Batch size is 100. So far I am seeing Postgres take roughly five times the > time it takes to do this in the Oracle.

Re: [PERFORM] Postgres batch write very slow - what to do

On 3/16/07, Merlin Moncure <[EMAIL PROTECTED]> wrote: Be careful...you are just testing one very specific thing and it its extremely possible that the Oracle JDBC batch insert is more optimized than PostgreSQL's. On my little pentium 4 workstation, by inserting 10 rows per insert: insert values

Re: [PERFORM] Postgres batch write very slow - what to do

On 3/16/07, Bob Dusek <[EMAIL PROTECTED]> wrote: This may or may not be related to what you're seeing... but, when we changed from Postgres 7.4.2 to 7.4.8, our batch processing slowed down fairly significantly. Here's what we were doing: Step 1) Build a larg file full of SQL insert statements.

Re: [PERFORM] Postgres batch write very slow - what to do

On 3/15/07, femski <[EMAIL PROTECTED]> wrote: I tried maxpages = 0 and full_page_writes=off and it seemed to be taking forever. All other tricks I have already tried. At this point I wondering if its a jdbc client side issue - I am using the latest 8.1. (as I said in an earlier post - I am usi

Re: [PERFORM] Determine dead tuples size

Alexey Romanchuk wrote: thanks, i install contribs and try to analyze result of pgstattuple function and found it strange. Try "SELECT * FROM pgstattuple('foo')", that'll tell you what the columns are. Take a look at README.pgstattuple as well for more details. -- Heikki Linnakangas Ente