pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedMapping a database completly into Memory
13+ messages / 7 participants
[nested] [flat]
* Mapping a database completly into Memory
@ 2003-07-27 08:49 Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 13+ messages in thread
From: Daniel Migowski @ 2003-07-27 08:49 UTC (permalink / raw)
To: pgsql-performance
Hallo pgsql-performance,
I just wondered if there is a possibility to map my database running
on a linux system completly into memory and to only use disk
accesses for writes.
I got a nice machine around with 2 gigs of ram, and my database at
the moment uses about 30MB on the disks.
Or does Postgresql do this automtatically, with some cache adjusting
parameters, and after doing a select * from <everything> on my
database?
Thank you and ciao,
Mig-O
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
@ 2003-07-27 16:18 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
0 siblings, 1 reply; 13+ messages in thread
From: Tom Lane @ 2003-07-27 16:18 UTC (permalink / raw)
To: Daniel Migowski <postgresql@Mig-O.de>; +Cc: pgsql-performance
Daniel Migowski <postgresql@Mig-O.de> writes:
> I just wondered if there is a possibility to map my database running
> on a linux system completly into memory and to only use disk
> accesses for writes.
That happens for free, if you have enough RAM. The kernel will use
spare RAM to hold copies of every disk block it's ever read.
regards, tom lane
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
@ 2003-07-28 04:14 ` Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
0 siblings, 1 reply; 13+ messages in thread
From: Josh Berkus @ 2003-07-28 04:14 UTC (permalink / raw)
To: Daniel Migowski <postgresql@Mig-O.de>; +Cc: pgsql-performance
Daniel,
> > I just wondered if there is a possibility to map my database running
> > on a linux system completly into memory and to only use disk
> > accesses for writes.
>
> That happens for free, if you have enough RAM. The kernel will use
> spare RAM to hold copies of every disk block it's ever read.
Also, don't forget to raise your effective_cache_size so that PostgreSQL
*knows* that you have lots of RAM.
--
Josh Berkus
Aglio Database Solutions
San Francisco
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
@ 2003-07-28 14:16 ` Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 13+ messages in thread
From: Franco Bruno Borghesi @ 2003-07-28 14:16 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: Daniel Migowski <postgresql@Mig-O.de>; pgsql-performance
wouldn't also increasing shared_buffers to 64 or 128 MB be a good
performance improvement? This way, pages belonging to heavily used
indexes would be already cached by the database itself.
Please, correct me if I'm wrong.
On Mon, 2003-07-28 at 01:14, Josh Berkus wrote:
> Daniel,
>
> > > I just wondered if there is a possibility to map my database running
> > > on a linux system completly into memory and to only use disk
> > > accesses for writes.
> >
> > That happens for free, if you have enough RAM. The kernel will use
> > spare RAM to hold copies of every disk block it's ever read.
>
> Also, don't forget to raise your effective_cache_size so that PostgreSQL
> *knows* that you have lots of RAM.
Attachments:
signature.asc (application/pgp-signature, 186B) download
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
@ 2003-07-28 16:25 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 16:50 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 18:20 ` Re: Mapping a database completly into Memory Andrew Sullivan <andrew@libertyrms.info>
2003-07-29 15:22 ` Re: Mapping a database completly into Memory Vivek Khera <khera@kcilink.com>
0 siblings, 3 replies; 13+ messages in thread
From: Tom Lane @ 2003-07-28 16:25 UTC (permalink / raw)
To: Franco Bruno Borghesi <franco@akyasociados.com.ar>; +Cc: Josh Berkus <josh@agliodbs.com>; Daniel Migowski <postgresql@Mig-O.de>; pgsql-performance
Franco Bruno Borghesi <franco@akyasociados.com.ar> writes:
> wouldn't also increasing shared_buffers to 64 or 128 MB be a good
> performance improvement? This way, pages belonging to heavily used
> indexes would be already cached by the database itself.
Not necessarily. The trouble with large shared_buffers settings is you
end up with lots of pages being doubly cached (both in PG's buffers and
in the kernel's disk cache), thus wasting RAM. If we had a portable way
of preventing the kernel from caching the same page, it would make more
sense to run with large shared_buffers.
regards, tom lane
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
@ 2003-07-28 16:50 ` Josh Berkus <josh@agliodbs.com>
2003-07-28 16:58 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 17:48 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
2 siblings, 2 replies; 13+ messages in thread
From: Josh Berkus @ 2003-07-28 16:50 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-performance
Tom,
> If we had a portable way
> of preventing the kernel from caching the same page, it would make more
> sense to run with large shared_buffers.
Really? I thought we wanted to move the other way ... that is, if we could
get over the portability issues, eliminate shared_buffers entirely and rely
completely on the OS cache.
--
Josh Berkus
Aglio Database Solutions
San Francisco
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 16:50 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
@ 2003-07-28 16:58 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 13+ messages in thread
From: Tom Lane @ 2003-07-28 16:58 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-performance
Josh Berkus <josh@agliodbs.com> writes:
>> If we had a portable way
>> of preventing the kernel from caching the same page, it would make more
>> sense to run with large shared_buffers.
> Really? I thought we wanted to move the other way ... that is, if we could
> get over the portability issues, eliminate shared_buffers entirely and rely
> completely on the OS cache.
That seems unlikely to happen: there are cache-coherency problems if you
don't do your page-level access through shared buffers. Some have
suggested using mmap access to the data files in place of shared memory,
but that introduces a slew of issues of its own. It might happen but
I'm not holding my breath.
regards, tom lane
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 16:50 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
@ 2003-07-28 17:48 ` Franco Bruno Borghesi <franco@akyasociados.com.ar>
1 sibling, 0 replies; 13+ messages in thread
From: Franco Bruno Borghesi @ 2003-07-28 17:48 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-performance
But I think it's still a good option.
For example, in servers where there are other applications running (a
web server, for example) that are constantly accesing the disk and
replacing cached postgresql pages in the kernel, having shared buffers
could reduce this efect and assure the precense of our pages in
memory... I gues :)
On Mon, 2003-07-28 at 13:50, Josh Berkus wrote:
> Tom,
>
> > If we had a portable way
> > of preventing the kernel from caching the same page, it would make more
> > sense to run with large shared_buffers.
>
> Really? I thought we wanted to move the other way ... that is, if we could
> get over the portability issues, eliminate shared_buffers entirely and rely
> completely on the OS cache.
Attachments:
signature.asc (application/pgp-signature, 186B) download
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
@ 2003-07-28 18:20 ` Andrew Sullivan <andrew@libertyrms.info>
2 siblings, 0 replies; 13+ messages in thread
From: Andrew Sullivan @ 2003-07-28 18:20 UTC (permalink / raw)
To: pgsql-performance
On Mon, Jul 28, 2003 at 12:25:57PM -0400, Tom Lane wrote:
> in the kernel's disk cache), thus wasting RAM. If we had a portable way
> of preventing the kernel from caching the same page, it would make more
> sense to run with large shared_buffers.
Plus, Postgres seems not to be very good at managing very large
buffer sets.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew@libertyrms.info> M2P 2A8
+1 416 646 3304 x110
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
@ 2003-07-29 15:22 ` Vivek Khera <khera@kcilink.com>
2003-07-30 22:10 ` Re: Mapping a database completly into Memory Bruce Momjian <pgman@candle.pha.pa.us>
2003-07-30 22:12 ` Re: Mapping a database completly into Memory Bruce Momjian <pgman@candle.pha.pa.us>
2 siblings, 2 replies; 13+ messages in thread
From: Vivek Khera @ 2003-07-29 15:22 UTC (permalink / raw)
To: pgsql-performance
>>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.us> writes:
TL> Franco Bruno Borghesi <franco@akyasociados.com.ar> writes:
>> wouldn't also increasing shared_buffers to 64 or 128 MB be a good
>> performance improvement? This way, pages belonging to heavily used
>> indexes would be already cached by the database itself.
TL> Not necessarily. The trouble with large shared_buffers settings is you
TL> end up with lots of pages being doubly cached (both in PG's buffers and
I think if you do a lot of inserting/updating to your table, then more
SHM is better (and very high fsm settings), since you defer pushing
out the dirty pages to the disk. For read-mostly, I agree that
letting the OS do the caching is a better way.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-29 15:22 ` Re: Mapping a database completly into Memory Vivek Khera <khera@kcilink.com>
@ 2003-07-30 22:10 ` Bruce Momjian <pgman@candle.pha.pa.us>
2003-07-31 14:15 ` Re: Mapping a database completly into Memory Vivek Khera <khera@kcilink.com>
1 sibling, 1 reply; 13+ messages in thread
From: Bruce Momjian @ 2003-07-30 22:10 UTC (permalink / raw)
To: Vivek Khera <khera@kcilink.com>; +Cc: pgsql-performance
I think it all depends on your working set. Having shared memory be
smaller than you working set causes pages to have to be copied in from
the kernel buffers (not a huge problem, but a small penalty), while
having shared memory larger than the working set causes overhead of
searching through all those buffers.
---------------------------------------------------------------------------
Vivek Khera wrote:
> >>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.us> writes:
>
> TL> Franco Bruno Borghesi <franco@akyasociados.com.ar> writes:
> >> wouldn't also increasing shared_buffers to 64 or 128 MB be a good
> >> performance improvement? This way, pages belonging to heavily used
> >> indexes would be already cached by the database itself.
>
> TL> Not necessarily. The trouble with large shared_buffers settings is you
> TL> end up with lots of pages being doubly cached (both in PG's buffers and
>
> I think if you do a lot of inserting/updating to your table, then more
> SHM is better (and very high fsm settings), since you defer pushing
> out the dirty pages to the disk. For read-mostly, I agree that
> letting the OS do the caching is a better way.
>
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Vivek Khera, Ph.D. Khera Communications, Inc.
> Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
> AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-29 15:22 ` Re: Mapping a database completly into Memory Vivek Khera <khera@kcilink.com>
2003-07-30 22:10 ` Re: Mapping a database completly into Memory Bruce Momjian <pgman@candle.pha.pa.us>
@ 2003-07-31 14:15 ` Vivek Khera <khera@kcilink.com>
0 siblings, 0 replies; 13+ messages in thread
From: Vivek Khera @ 2003-07-31 14:15 UTC (permalink / raw)
To: pgsql-performance
>>>>> "BM" == Bruce Momjian <pgman@candle.pha.pa.us> writes:
BM> I think it all depends on your working set. Having shared memory be
BM> smaller than you working set causes pages to have to be copied in from
BM> the kernel buffers (not a huge problem, but a small penalty), while
BM> having shared memory larger than the working set causes overhead of
BM> searching through all those buffers.
i.e., It is a black art, and no single piece of advice can be taken in
isolation ;-(
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Mapping a database completly into Memory
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Re: Mapping a database completly into Memory Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Re: Mapping a database completly into Memory Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Re: Mapping a database completly into Memory Tom Lane <tgl@sss.pgh.pa.us>
2003-07-29 15:22 ` Re: Mapping a database completly into Memory Vivek Khera <khera@kcilink.com>
@ 2003-07-30 22:12 ` Bruce Momjian <pgman@candle.pha.pa.us>
1 sibling, 0 replies; 13+ messages in thread
From: Bruce Momjian @ 2003-07-30 22:12 UTC (permalink / raw)
To: Vivek Khera <khera@kcilink.com>; +Cc: pgsql-performance
You make an interesting distinction that read/write needs more shared
memory. I think this is because if you want to reused a read-only
shared buffer, you can just throw away the contents, while a dirty
buffer requires you to write it into the kernel before you can use it.
---------------------------------------------------------------------------
Vivek Khera wrote:
> >>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.us> writes:
>
> TL> Franco Bruno Borghesi <franco@akyasociados.com.ar> writes:
> >> wouldn't also increasing shared_buffers to 64 or 128 MB be a good
> >> performance improvement? This way, pages belonging to heavily used
> >> indexes would be already cached by the database itself.
>
> TL> Not necessarily. The trouble with large shared_buffers settings is you
> TL> end up with lots of pages being doubly cached (both in PG's buffers and
>
> I think if you do a lot of inserting/updating to your table, then more
> SHM is better (and very high fsm settings), since you defer pushing
> out the dirty pages to the disk. For read-mostly, I agree that
> letting the OS do the caching is a better way.
>
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Vivek Khera, Ph.D. Khera Communications, Inc.
> Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
> AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 13+ messages in thread
end of thread, other threads:[~2003-07-31 14:15 UTC | newest]
Thread overview: 13+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-07-27 08:49 Mapping a database completly into Memory Daniel Migowski <postgresql@Mig-O.de>
2003-07-27 16:18 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 04:14 ` Josh Berkus <josh@agliodbs.com>
2003-07-28 14:16 ` Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 16:25 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 16:50 ` Josh Berkus <josh@agliodbs.com>
2003-07-28 16:58 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-07-28 17:48 ` Franco Bruno Borghesi <franco@akyasociados.com.ar>
2003-07-28 18:20 ` Andrew Sullivan <andrew@libertyrms.info>
2003-07-29 15:22 ` Vivek Khera <khera@kcilink.com>
2003-07-30 22:10 ` Bruce Momjian <pgman@candle.pha.pa.us>
2003-07-31 14:15 ` Vivek Khera <khera@kcilink.com>
2003-07-30 22:12 ` Bruce Momjian <pgman@candle.pha.pa.us>
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