Having been a C/C++ developer many years before being a DBA, and having
written ITIL software; How is migrating structure from a Development
database to a test database whilst maintaining test data backwards?
Besides, the OP was asking how to diff to databases and create ddl, not
asking for us to
On Thu, Jan 20, 2011 at 5:00 AM, French, Martin fren...@cromwell.co.uk wrote:
Having been a C/C++ developer many years before being a DBA, and having
written ITIL software; How is migrating structure from a Development
database to a test database whilst maintaining test data backwards?
It's
On Thu, Jan 20, 2011 at 5:00 AM, French, Martin fren...@cromwell.co.uk wrote:
Personally, I'd rather
not go trawling through what can only be described as hundreds of
thousands of lines of PostgreSQL log to find THE RIGHT DDL statements.
Oh that's easy. Grep out the statements that start
On Thu, Jan 20, 2011 at 8:46 AM, Scott Marlowe scott.marl...@gmail.com wrote:
On Thu, Jan 20, 2011 at 5:00 AM, French, Martin fren...@cromwell.co.uk
wrote:
Personally, I'd rather
not go trawling through what can only be described as hundreds of
thousands of lines of PostgreSQL log to find
Hi All;
I suspect I know the answer to this...
What's the current state of multi-master replication for PostgreSQL? Is
Bucardo the only true master/master solution out there that might be
worthy of a production push? Is Postres-R a candidate at this point (I
suspect not)? Are there any
On Thu, Jan 20, 2011 at 9:53 AM, CS DBA cs_...@consistentstate.com wrote:
Hi All;
I suspect I know the answer to this...
What's the current state of multi-master replication for PostgreSQL? Is
Bucardo the only true master/master solution out there that might be worthy
of a production push?
Thanks Scott... a couple comments.
Our developers never decide what goes to where... they just happily plumb
away on the development db until we're ready to take our product to testing
(at regular intervals), once QA is passed, we wish to apply these to live.
We have several diff tools and sync
On Thu, Jan 20, 2011 at 10:42 AM, Bradley Holbrook
operations_brad...@servillian.ca wrote:
Thanks Scott... a couple comments.
Our developers never decide what goes to where... they just happily plumb
away on the development db until we're ready to take our product to testing
(at regular
Followup, note that you can set the log_statement='ddl' for an entire
pg cluster, for a single database, or for a single user, if that
helps. logging ddl does not log dml, or data changes, just structural
changes.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
scott.marl...@gmail.com (Scott Marlowe) writes:
On Thu, Jan 20, 2011 at 9:53 AM, CS DBA cs_...@consistentstate.com wrote:
Hi All;
I suspect I know the answer to this...
What's the current state of multi-master replication for PostgreSQL? Is
Bucardo the only true master/master solution out
On Thu, Jan 20, 2011 at 10:52 AM, Scott Marlowe scott.marl...@gmail.com wrote:
Followup, note that you can set the log_statement='ddl' for an entire
pg cluster, for a single database, or for a single user, if that
helps. logging ddl does not log dml, or data changes, just structural
changes.
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: Thursday, January 20, 2011 12:51 PM
To: Bradley Holbrook
Cc: French, Martin; pgsql-admin@postgresql.org
Subject: Re: Postgres Backup Utility
On Thu, Jan 20, 2011 at 10:42 AM, Bradley Holbrook
On Thu, Jan 20, 2011 at 10:42 AM, Bradley Holbrook
operations_brad...@servillian.ca wrote:
Thanks Scott... a couple comments.
Our developers never decide what goes to where... they just happily
plumb away on the development db until we're ready to take
our product
to testing (at regular
Tom Lane wrote:
Lou Picciano loupicci...@comcast.net writes:
Sure - of course - performance, too! It just seems like such an obvious
candidate for a configurable option; I'm a bit surprised it isn't in
there... L
It *is* configurable: make pg_xlog a symlink. The reason we don't
On Jan 20, 2011, at 12:42 PM, Bradley Holbrook wrote:
Our developers never decide what goes to where... they just happily plumb
away on the development db until we're ready to take our product to testing
(at regular intervals), once QA is passed, we wish to apply these to live.
We have
On Thu, Jan 20, 2011 at 6:08 PM, John DeSoi de...@pgedit.com wrote:
On Jan 20, 2011, at 12:42 PM, Bradley Holbrook wrote:
Our developers never decide what goes to where... they just happily plumb
away on the development db until we're ready to take our product to testing
(at regular
Hi all..
Start from vacuum feature information from PGSQL helps documentation, it
telling me that Postgresql didn't delete data permanently when we execute
delete command, it just made the data invalid. By following this email
archive :
17 matches
Mail list logo
