On Jan 20, 2011, at 10:42 AM, Bradley Holbrook wrote:
Martin French is right though, ask your developers to write down all their
SQL struct changes and they look at you funny... and being a developer
myself I'd look at me funny.
Well, it's what I do and it's trivial. Just don't type DDL
: Re: [ADMIN] Postgres Backup Utility
On Wed, Jan 19, 2011 at 12:12 AM, French, Martin
fren...@cromwell.co.uk wrote:
Ok, you say that you cannot drop and recreate, so you need to do this
via
alter statements only? That's obviously going to complicate matters,
as a
straight dump, drop, recreate
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
: Re: [ADMIN] Postgres Backup Utility
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
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
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
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
-admin@postgresql.org
Subject: RE: [ADMIN] Postgres Backup Utility
Well,
I can’t just go dropping and recreating tables… it needs to create
the correct alter statements if existing tables and or functions already exist.
Secondly,
when I’m finished changing the structure, I need
On Wed, Jan 19, 2011 at 12:12 AM, French, Martin fren...@cromwell.co.uk wrote:
Ok, you say that you cannot drop and recreate, so you need to do this via
alter statements only? That’s obviously going to complicate matters, as a
straight dump, drop, recreate, restore would be the fastest and by
something very similar with Oracle a few years back.
Cheers
Martin
From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Bradley Holbrook
Sent: 18 January 2011 00:08
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Postgres Backup Utility
Hello
...@cromwell.co.uk]
Sent: January-18-11 5:47 AM
To: Bradley Holbrook; pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Postgres Backup Utility
I'm assuming that this needs to be tightly controlled and as such a
replication tool is out of the question?
In that case; The first thing to pop into my
From: Bradley Holbrook [mailto:operations_brad...@servillian.ca]
Sent: 18 January 2011 16:57
To: French, Martin
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Postgres Backup Utility
Well, I can't just go dropping and recreating tables... it needs to
create the correct alter statements
Hello!
First day on the new mailing list as I have need of some expert's advice.
I need to be able to quickly apply the structure updates from a development
database to a testing database, and do selective data updates (like on
lookup tables, but not content tables).
Any help would be
19 matches
Mail list logo
