On Mon, 2007-11-19 at 18:38 -0500, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Reason to do this now: Perf Tips have been changed for 8.3 to recommend
> > using --single-transaction when restoring pg_dumps, because of fast COPY
> > enhancement. Allowing this to cause an error will
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> This is an extremely poorly phrased TODO item.
>
> > OK, updated:
>
> > o Prevent COMMENT ON dbname from issuing a warning when loading
> > into a database with a different name, perhaps using C
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This is an extremely poorly phrased TODO item.
> OK, updated:
> o Prevent COMMENT ON dbname from issuing a warning when loading
> into a database with a different name, perhaps using COMMENT ON
> CURRENT DA
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have added a TODO item:
>
> > o Allow COMMENT ON dbname to work when loading into a database
> > with a different name
>
> This is an extremely poorly phrased TODO item. The problem is not that
> you can't commen
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I have added a TODO item:
> o Allow COMMENT ON dbname to work when loading into a database
> with a different name
This is an extremely poorly phrased TODO item. The problem is not that
you can't comment on a database with a different
Simon Riggs <[EMAIL PROTECTED]> writes:
> Reason to do this now: Perf Tips have been changed for 8.3 to recommend
> using --single-transaction when restoring pg_dumps, because of fast COPY
> enhancement. Allowing this to cause an error will prevent the whole dump
> from restoring.
If it were indee
On Mon, 2007-11-19 at 14:27 -0500, Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > Malcus Imhof wrote:
> >
> > > Yea, the dump thinks it is going into the same database. I don't see
> > > any way of fixing that. We don't allow functions for the object name.
> > > If
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Malcus Imhof wrote:
>
> > Yea, the dump thinks it is going into the same database. I don't see
> > any way of fixing that. We don't allow functions for the object name.
> > If we did we could use current_database(). Fortunately I think it is
> >
Bruce Momjian wrote:
> Malcus Imhof wrote:
> Yea, the dump thinks it is going into the same database. I don't see
> any way of fixing that. We don't allow functions for the object name.
> If we did we could use current_database(). Fortunately I think it is
> the only place where the database n
Malcus Imhof wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3760
> Logged by: Malcus Imhof
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.5
> Operating system: Windows 2003
> Description:Comment on restore database
> Details:
>
The following bug has been logged online:
Bug reference: 3760
Logged by: Malcus Imhof
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Windows 2003
Description:Comment on restore database
Details:
When I'm restoring a dump done in a datab
11 matches
Mail list logo
