"Kasia Tuszynska" writes:
> Description:pg_restore is done in alphabetical order by schema
You have not shown us any actual problem. There is nothing wrong with
restoring the data in the order pg_dump uses, because no triggers or
cross-table constraints have been installed at the time th
The following bug has been logged online:
Bug reference: 4777
Logged by: Kasia Tuszynska
Email address: ktuszyn...@esri.com
PostgreSQL version: 8.3.7
Operating system: Windows 2003 server
Description:pg_restore is done in alphabetical order by schema
Details:
Summar
On Apr 23, 11:30 am, Kevin Field wrote:
>
> pg_restore: WARNING: database "production" does not exist
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
> pg_restore: [archiver (db)] Error from TOC entry 519; 2612 47275
> PROCEDURAL LANGUAGE plperl mysuperuser
> pg_restore: [archiver (db)]
On Thu, Apr 23, 2009 at 6:43 PM, Kevin Field wrote:
> On Apr 23, 12:13 pm, dp...@pgadmin.org (Dave Page) wrote:
>> On Thu, Apr 23, 2009 at 4:30 PM, Kevin Field
>> wrote:
>> > Is it possible it's looking for Perl in the wrong place? (Hence the
>> > "No such file..." error that somehow makes it b
On Apr 23, 12:13 pm, dp...@pgadmin.org (Dave Page) wrote:
> On Thu, Apr 23, 2009 at 4:30 PM, Kevin Field
> wrote:
> > Is it possible it's looking for Perl in the wrong place? (Hence the
> > "No such file..." error that somehow makes it back to my Perl script?)
>
> What version of perl do you hav
On Thu, Apr 23, 2009 at 4:30 PM, Kevin Field wrote:
> Is it possible it's looking for Perl in the wrong place? (Hence the
> "No such file..." error that somehow makes it back to my Perl script?)
What version of perl do you have?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
> However, after that when I try to run a script to dump another database and
> restore it onto the beta, I get a "file not found" error, which is really
> odd both because it was working fine on the 2009-03-24 build and because the
> permissions have not changed. Aside from that, which is it's ow
Christine,
when PostgreSQL does not start on Windows, the first place to look for
errors is the Microsoft Windows EventLog. That is the standard place to
report errors.
You can dig there via Control Panel; exact click path depending on your
Windows Version (XP / Vista / W2003 / W2008 / W7); or st
