pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Somasekhar Bangalore <sbangalore@zensutra.com>
Cc: Jaime Casanova <el_vigia_ec@hotmail.com>
Cc: pgsql-general@postgresql.org, pgsql-hackers@postgresql.org, pgsql-admin@postgresql.org, K Harikumar <kharikumar@zensutra.com>
Cc: Anoop G <ganoop@zensutra.com>
Cc: Sanjay Rathod <srathod@zensutra.com>
Subject: Re: [GENERAL][HACKERS]data fragmentation
Date: Wed, 24 Dec 2003 16:28:58 -0800
Message-ID: <3FEA2F4A.9000503@commandprompt.com> (raw)
In-Reply-To: <BF493B193A334743AA9EF48945E69C13519176@exchange.india.zensutra.com>
References: <BF493B193A334743AA9EF48945E69C13519176@exchange.india.zensutra.com>

Hello,

  An quicker option would be to use rsync (on a stopped database of 
course). You can rsync to a new directory (off the filesystem) and then 
reformat the data filesystem and move it back.

J


Somasekhar Bangalore wrote:

>Hi,
>
>I too had the same problem;  There was one query which used to take a very long time. What I did was, I took a backup of the whole database. Reinstalled postgres on a different mount point and restored the data back into the new database. Now my queries are running faster. Try it. All the very best.
>
>Somasekhar
>
>
>-----Original Message-----
>From: Jaime Casanova [mailto:el_vigia_ec@hotmail.com]
>Sent: Friday, December 12, 2003 3:07 AM
>To: pgsql-general@postgresql.org; pgsql-hackers@postgresql.org; pgsql-admin@postgresql.org
>Subject: [GENERAL][ADMIN][HACKERS]data fragmentation
>
>Hi,
>
>i have a theorical question. i was thought that data fragmentation can cause
>a
>loss of performance when retrieving data from a database. Some DBMS solved
>this
>with dbspaces, but postgresql doesn't support this concept.
>so, pgsql databases tend to suffer from data fragmentation?
>if yes, what is the solution you recommend?
>
>also i was thought that even when DBMS support dbspaces DELETEing records
>may
>cause data fragmentation anyway.
>so, can i think of DELETE statement as a double-edged sword?
>it is indifferent in pgsql - it doesn't support dbspaces anyway?
>
>thanks in advance,
>Jaime Casanova (el_vigia)
>
>_________________________________________________________________
>The new MSN 8: smart spam protection and 2 months FREE* 
>http://join.msn.com/?page=features/junkmail
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>               http://archives.postgresql.org
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
>    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>  
>

-- 
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC - S/JDBC
Postgresql support, programming, shared hosting and dedicated hosting.
+1-503-222-2783 - jd@commandprompt.com - http://www.commandprompt.com





view thread (4+ messages)

Message-ID: <3FEA2F4A.9000503@commandprompt.com>
Permalink:  ../3FEA2F4A.9000503@commandprompt.com/
Also on:    postgresql.org/message-id/3FEA2F4A.9000503@commandprompt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jd@commandprompt.com, sbangalore@zensutra.com, el_vigia_ec@hotmail.com, kharikumar@zensutra.com, ganoop@zensutra.com, srathod@zensutra.com
  Subject: Re: [GENERAL][HACKERS]data fragmentation
  In-Reply-To: <3FEA2F4A.9000503@commandprompt.com>
  References: <BF493B193A334743AA9EF48945E69C13519176@exchange.india.zensutra.com> <3FEA2F4A.9000503@commandprompt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox