Обсуждение: pgAdmin 1.14 bug - Backup globals error

<div class="WordSection1"><p class="MsoNormal">Hi,<p class="MsoNormal"> <p class="MsoNormal">The “Backup Globals…” menu
item(when right-clicking on server node and selecting from pop-up menu) gives the following error when executed:<p
class="MsoNormal"> <pclass="MsoNormal"><span style="color:#0070C0">D:\Program Files\PostgreSQL\9.1\bin\pg_dump.exe
--hostlocalhost --port 5432 --username "postgres" --no-password  --verbose --file "C:\tmp\BackupFile.sql"
--globals-only</span><pclass="MsoNormal"><span style="color:#0070C0">D:\Program Files\PostgreSQL\9.1\bin\pg_dump.exe:
illegaloption -- globals-only</span><p class="MsoNormal"><span style="color:#0070C0">Try "pg_dump --help" for more
information.</span><pclass="MsoNormal"><span style="color:#0070C0"> </span><p class="MsoNormal"><span
style="color:#0070C0">Processreturned exit code 1.</span><p class="MsoNormal"> <p class="MsoNormal">Should the
generatedcommand be using pg_dumpall instead of pg_dump?<p class="MsoNormal"> <p class="MsoNormal">I’m using pgAdmin
IIIVersion 1.14.0 with PostgreSQL 9.1.1 running on 64-bit Windows Server 2008.<p class="MsoNormal"> <p
class="MsoNormal">Thanks.<pclass="MsoNormal"> <p class="MsoNormal">Regards,<p class="MsoNormal">Chris Price<p
class="MsoNormal"> </div>

Hi,

On Thu, 2011-12-08 at 23:04 +1100, Chris Price wrote:
> [...] 
> 
> The "Backup Globals." menu item (when right-clicking on server node and
> selecting from pop-up menu) gives the following error when executed:
> 
>  
> 
> D:\Program Files\PostgreSQL\9.1\bin\pg_dump.exe --host localhost --port 5432
> --username "postgres" --no-password  --verbose --file
> "C:\tmp\BackupFile.sql" --globals-only
> 
> D:\Program Files\PostgreSQL\9.1\bin\pg_dump.exe: illegal option --
> globals-only
> 
> Try "pg_dump --help" for more information.
> 
>  
> 
> Process returned exit code 1.
> 
>  
> 
> Should the generated command be using pg_dumpall instead of pg_dump?
> 

Yes.

> I'm using pgAdmin III Version 1.14.0 with PostgreSQL 9.1.1 running on 64-bit
> Windows Server 2008.
> 

That's your issue. You should use 1.14.1 instead. Update, and your issue
should go away :)


-- 
Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com