On mié, 2014-04-02 at 09:05 -0700, l...@fastmail.us wrote:
> Hello,
>
> I am hoping to install pgadmin3 for centos 5.10 x86_64, but the one
> available in the repo is i386. Is this an error, or is x86_64 not
> available?
http://pkgs.org/centos-5/epel-x86_64/pgadmin3-1.8.4-1.el5.x86_64.rpm.html
>
We are using dedicated DB and DB Backup Server configured for Warm Standby.
Uptill now our Server was generating around 3k Wal files per day and backup
was catching up. Recently the load on our Production Server has increased
and now it is generating around 4k wal files.
Now we can see alot of wa
Hi Haroon,
On Thu, Apr 3, 2014 at 7:23 PM, Haroon wrote:
> We are using dedicated DB and DB Backup Server configured for Warm Standby.
> Uptill now our Server was generating around 3k Wal files per day and backup
> was catching up. Recently the load on our Production Server has increased
> and n
Hi-
Apologies if I missed this somewhere online, but I am wondering: when will
pgadmin version 1.18.2 or higher be released? I made a bug report in February
and Dinesh Kumar kindly let me know it had been fixed, but I still haven't seen
a release of a new version incorporating that fix at:
ht
Thanks for your response. pkgs.org is good to know about, but the
version of pgadmin available there (1.8.4) seems to be incompatible with
PostgreSQL 9.3. I will stick with the command line until our next server
upgrade. Thank you again-
On Thu, Apr 3, 2014, at 2:17, jaime soler wrote:
> On mié, 2
On Thu, 2014-04-03 at 10:31 -0700, l...@fastmail.us wrote:
> Thanks for your response. pkgs.org is good to know about, but the
> version of pgadmin available there (1.8.4) seems to be incompatible with
> PostgreSQL 9.3. I will stick with the command line until our next server
> upgrade. Thank you a
On Thu, 2014-04-03 at 12:05 -0400, David Elbert wrote:
> Hi-
>
> Apologies if I missed this somewhere online, but I am wondering: when will
> pgadmin version 1.18.2 or higher be released? I made a bug report in
> February and Dinesh Kumar kindly let me know it had been fixed, but I still
> hav