Re: Patch to fix search_path defencies with pg_bench - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Patch to fix search_path defencies with pg_bench
Date
Msg-id 24357.1241637485@sss.pgh.pa.us
Whole thread Raw
In response to Re: Patch to fix search_path defencies with pg_bench  ("Dickson S. Guedes" <listas@guedesoft.net>)
Responses Re: Patch to fix search_path defencies with pg_bench  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
"Dickson S. Guedes" <listas@guedesoft.net> writes:
> Em Qua, 2009-05-06 �s 09:37 -0400, Tom Lane escreveu:
>> Seems like the right policy for that is "run pgbench in its own
>> database". 

> A text warning about this could be shown at start of pgbench if the
> target database isn't named "pgbench", for examplo, or just some text
> could be added to the docs.

There already is a prominent warning in the pgbench docs:
    Caution
pgbench -i creates four tables accounts, branches, history, andtellers, destroying any existing tables of these names.
Beverycareful to use another database if you have tables having thesenames!
 
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: lazy vacuum blocks analyze
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Patch to fix search_path defencies with pg_bench