> Could you look at this for Itagaki-san please? I can see the text in
> the po file, but I'm afraid my editor (or I!) will break the file and
> I have no meaningful way of testing it.
Recently, Mr. Saito is very busy.
I fixed it and sent to Guillaume
Regards.
Le jeudi 19 mars 2009 à 11:26:22, Glyn Astill a écrit :
> --- On Thu, 19/3/09, Dave Page wrote:
> > This is a limitation in the server. The pg_logdir_ls
> > function needs
> > the default logfile format to ensure it can reliably figure
> > out the
> > log date:
> >
> > if (strcmp(Log_filen
On Thu, Mar 19, 2009 at 10:46 AM, David Gould wrote:
> What actually happens is that when you enter the backup window and click
> "OK" it flicks over to the Messages screen, but nothing happens. A backup
> file appears but it's 0 bytes in length.
It sounds like it's starting the backup. Does th
Thanks for your prompt response.
I am currently running pgAdmin 1.8.4 on Vista for backup and XP for
restore. Server is 8.3.6 on the local machine in both cases.
Dave Page wrote:
On Thu, Mar 19, 2009 at 9:08 AM, David Gould wrote:
Hello,
There are a couple of bugs surrounding backup/re
--- On Thu, 19/3/09, Dave Page wrote:
>
> This is a limitation in the server. The pg_logdir_ls
> function needs
> the default logfile format to ensure it can reliably figure
> out the
> log date:
>
> if (strcmp(Log_filename,
> "postgresql-%Y-%m-%d_%H%M%S.log") != 0)
> er
On Thu, Mar 19, 2009 at 9:43 AM, Glyn Astill wrote:
>
> I've been playing with this again this morning and I've noticed the "server
> status" panel is now much nicer.
>
> However one thing that has always tripped me up is that it expects the
> log_filename to be of the format "postgresql-%Y-%m-%
Hi Ray, sorry for the delay in replying to this.
On Mon, Mar 16, 2009 at 6:12 PM, Raymond O'Donnell wrote:
> Hi Dave & developers,
>
> Would it be a good idea to have the block indent/unindent and block
> comment/uncomment features appear as items on the "Edit" menu, along
> with their associated
I've been playing with this again this morning and I've noticed the "server
status" panel is now much nicer.
However one thing that has always tripped me up is that it expects the
log_filename to be of the format "postgresql-%Y-%m-%d_%H%M%S.log", but I've
always logged into one file for each d
On Thu, Mar 19, 2009 at 9:08 AM, David Gould wrote:
> Hello,
>
> There are a couple of bugs surrounding backup/restore.
>
> When you go to backup it doesn't just work - I haven't played around with
> settings. On the command line it suggest that it's tried:
>
> pg_dump... -F -p ...
>
> Where what
Hello,
There are a couple of bugs surrounding backup/restore.
When you go to backup it doesn't just work - I haven't played around
with settings. On the command line it suggest that it's tried:
pg_dump... -F -p ...
Where what it should generate is:
pg_dump... -F p ...
Worse, you can't co
Hi Hiroshi,
Could you look at this for Itagaki-san please? I can see the text in
the po file, but I'm afraid my editor (or I!) will break the file and
I have no meaningful way of testing it.
Thanks for the bug report Itagaki-san.
On Thu, Mar 19, 2009 at 7:02 AM, Takahiro Itagaki
wrote:
> A menu
On Thu, Mar 19, 2009 at 2:52 AM, Andrew Maclean
wrote:
> Two things:
> 1) Has the mixed slashes on the certificate file been fixed?
Thats a bug in PostgreSQL's libpq library, not pgAdmin. A fix is being
discussed though.
> 2) With respect to the error: "Error connecting to server: root
> certifi
A menu text is broken in Japanese version of v1.10.0 beta.
The location is "Query Tool > "Query" > "Execute as Script(p|F6)"
Probably there is a typo in the text for keyboard shortcut.
It shows (p|F6) and F6 key is unusable.
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.or
13 matches
Mail list logo
