Re: [HACKERS] large object regression tests

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Jeremy Drake <pgsql(at)jdrake(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL-development <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] large object regression tests
Date: 2006-10-15 03:11:10
Message-ID: 200610150311.k9F3BAk03921@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


Sorry, please disregard. Was means for a Japanese FAQ update.

---------------------------------------------------------------------------

Bruce Momjian wrote:
>
> Patch applied. Thanks.
>
> ---------------------------------------------------------------------------
>
>
> Jeremy Drake wrote:
> > On Sun, 24 Sep 2006, Jeremy Drake wrote:
> >
> > > On Thu, 21 Sep 2006, Tom Lane wrote:
> > >
> > > > I think we could do without the Moby Dick extract too ...
> > >
> > > I am open to suggestions. I saw one suggestion that I use an image of an
> > > elephant, but I suspect that was tongue-in-cheek. I am not very fond of
> > > the idea of generating repetitious data, as I think it would be more
> > > difficult to determine whether or not the loseek/tell functions put me in
> > > the right place in the middle of the file.
> >
> > I just had the idea that I could use one of the existing data files which
> > are used for testing COPY instead of the Moby Dick extract. They are
> > already there, a few of them are pretty good sized, they have data in the
> > file which is not just simple repetition so it would be pretty obvious if
> > the seek function broke, and they are very unlikely to change. I am
> > considering changing the test I put together to use tenk.data as the input
> > file tomorrow and send in what I have again, since I also am doing a test
> > of \lo_import (which also requires a patch to psql I sent in earlier to
> > fix the output of the \lo_* commands to respect the output settings).
> >
> > --
> > When does summertime come to Minnesota, you ask?
> > Well, last year, I think it was a Tuesday.
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/docs/faq
>
> --
> Bruce Momjian bruce(at)momjian(dot)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 majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Schaber 2006-10-15 09:16:12 Re: GROUP BY on a large table -- an idea
Previous Message Bruce Momjian 2006-10-15 03:10:21 Re: [HACKERS] large object regression tests

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2006-10-15 16:22:33 Re: index advisor
Previous Message Bruce Momjian 2006-10-15 03:10:21 Re: [HACKERS] large object regression tests