From: | Scott Bailey <artacus(at)comcast(dot)net> |
---|---|
To: | Daniel Shane <shaned(at)LEXUM(dot)UMontreal(dot)CA> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tips/Hacks to create minial DB from the execution of several (simple) SQL requests. |
Date: | 2009-10-09 05:24:38 |
Message-ID: | 4ACEC916.8080504@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Daniel Shane wrote:
> Hi Scott!
>
> The problem is that my test database has several tables with many links between them, so I have no idea which 1000 rows to get from which table. The only thing I can do is run the program that connects to that database and tell it to run on a sample of the database.
>
> I can get a log of all the queries that are executed, but I was wondering if there was a more general solution where I could use a "modified/hacked" postgres driver and catch all the rows of all the tables that were accessed during those queries.
>
> I could then simply insert them into the test database and in theory my program should run the same if I used it instead of the real one (assuming its configure to run on the same sample).
>
> Daniel Shane
Yeah, still a much easier way. If there are many links between the
tables, then related records would typically be inserted either in the
same transaction or soon there after. You can use the xmin columns to
copy related rows from all tables.
Scott
From | Date | Subject | |
---|---|---|---|
Next Message | Mitesh51 | 2009-10-09 06:48:29 | Re: How to reduce WAL file Size |
Previous Message | Lew | 2009-10-09 03:34:38 | Re: Best data type to use for sales tax percent |