On Thu, Jun 30, 2016 at 1:38 PM, Murphy, Kevin
wrote:
> Is it expected that "grant * on database" grants are dumped only by
> `pg_dumpall -s` and not by `pg_dump -s` or `pg_dumpall -g`?
>
> Some people might assume that to restore a cluster it should be sufficient
> to
On Thu, Jun 30, 2016 at 3:53 AM, Chris Lewis wrote:
> Hello,
>
> We have 2 postgresql servers (v 9.4.2) master and slave in streaming
> replication. The overall cluster is controlled using pacemaker & corosync
> and the pgsql cluster agent which handles failover to, and
Is it expected that "grant * on database" grants are dumped only by `pg_dumpall
-s` and not by `pg_dump -s` or `pg_dumpall -g`?
Some people might assume that to restore a cluster it should be sufficient to
restore pg_dumpall globals output followed by individual pg_dump output.
Seemingly, this
On 06/30/2016 10:08 AM, Hanan Brener wrote:
The Postgresql server 9.5 installed from (www.enterprisedb.com/)
I don't know how you would do that.
I saw(sort of) your post on the EDB forum:
http://forums.enterprisedb.com/jforum.page?module=search=search=3_type=all_keywords=ruby
Clicking on
The Postgresql server 9.5 installed from (www.enterprisedb.com/)
Hanan Brener
Database and Data Collection Team Leader
Allot Communications
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Thursday, June 30, 2016 7:47 PM
To: Hanan Brener
On 06/30/2016 09:24 AM, Hanan Brener wrote:
Installing on Centos 6 PostgreSQL 9.5 (64 bit) ; ruby 1.8
How did you install the Postgres server?
and get from
*https://pkgs.org/centos-6/epel-x86_64/postgresql-plruby-0.5.3-4.el6.x86_64.rpm.html*
I would say where you install plruby from
Hanan Brener writes:
> Installing on Centos 6 PostgreSQL 9.5 (64 bit) ; ruby 1.8
> and get from
> https://pkgs.org/centos-6/epel-x86_64/postgresql-plruby-0.5.3-4.el6.x86_64.rpm.html
> - plruby libraries(postgresql-plruby-0.5.3-4.el6.x86_64).
> Additional installed
Installing on Centos 6 PostgreSQL 9.5 (64 bit) ; ruby 1.8
and get from
https://pkgs.org/centos-6/epel-x86_64/postgresql-plruby-0.5.3-4.el6.x86_64.rpm.html
- plruby libraries(postgresql-plruby-0.5.3-4.el6.x86_64).
Additional installed postgresql95-libs
On Wed, Jun 29, 2016 at 1:46 PM, Neil Anderson wrote:
> On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
>>
>> Elsewhere, somebody was asking how people implemented version control
>> for stored procedures on (MS) SQL Server.
>>
>> The consensus was that this is probably
On Thu, Jun 30, 2016 at 7:15 AM, Nick Babadzhanian wrote:
> Setup:
> 2 PostgreSQL servers are geographically spread. The first one is used for an
> application that gathers data. It is connected to the second database that is
> used to process the said data. Connection is not
Mike Sofen wrote:
-Original Message-
From: Mark Morgan Lloyd Sent: Thursday, June 30, 2016 2:41 AM
Neil Anderson wrote:
On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
Elsewhere, somebody was asking how people implemented version control
for stored procedures on (MS) SQL
Greetings,
* Kaixi Luo (kaixi...@gmail.com) wrote:
> We use PostgreSQL at work and we do daily backups with pg_dump. After that
> we pg_restore the dump and check the database that there isn't any data
> corruption. As the database grows, the whole pg_dump / pg_restore cycle
> time is quickly
On Thu, Jun 30, 2016 at 9:00 PM, Kaixi Luo wrote:
>> Before replaying a backup on a production system, you would need a
>> pre-production setup where the backup is replayed and checked.
>> Honestly, you can only be sure that a backup is working correctly
>> after reusing it.
Setup:
2 PostgreSQL servers are geographically spread. The first one is used for an
application that gathers data. It is connected to the second database that is
used to process the said data. Connection is not very stable nor is it fast, so
using Bidirectional replication is not an option. It
-Original Message-
>From: Mark Morgan Lloyd Sent: Thursday, June 30, 2016 2:41 AM
>Neil Anderson wrote:
>> On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
>>> Elsewhere, somebody was asking how people implemented version control
>>> for stored procedures on (MS) SQL Server.
>>>
>
> Before replaying a backup on a production system, you would need a
> pre-production setup where the backup is replayed and checked.
> Honestly, you can only be sure that a backup is working correctly
> after reusing it. You could always do some validation of the raw
> backup contents, but you
Hello,
We have 2 postgresql servers (v 9.4.2) master and slave in streaming
replication. The overall cluster is controlled using pacemaker &
corosync and the pgsql cluster agent which handles failover to, and
promotion of, the slave.
Recently a failover occured and I noticed that log
On 29.06.2016 17:51, Kaixi Luo wrote:
Hello,
We use PostgreSQL at work and we do daily backups with pg_dump. After
that we pg_restore the dump and check the database that there isn't
any data corruption. As the database grows, the whole pg_dump /
pg_restore cycle time is quickly approaching
Neil Anderson wrote:
On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
Elsewhere, somebody was asking how people implemented version control
for stored procedures on (MS) SQL Server.
The consensus was that this is probably best managed by using scripts or
command files to generate stored
19 matches
Mail list logo