I’m quite often doing stuff on remote machines, and quite frequently I start some long-running job, when I remember that I didn’t ran it via screen – so it will break, if my network connection will die.
Is there any sane way to start screen automatically? YES.
On 24th of August, Takahiro Itagaki committed patch:
Log Message:
-----------
Add string functions: concat(), concat_ws(), left(), right(), and reverse().
Pavel Stehule, reviewed by me.
Every now and then somebody asks how to make diff of database schemata.
Usual background is like: we have production database, and development database, and we want to see what is different on development to be able to change production in the same way.
Personally I think that such approach is inherently flawed. Why?
Well, the biggest information is that hot-backups on slave work. And they work fine. Really fine.
Some more information (with nice graph!):
“Zainspirowany” pismem o kuchni amerykańskiej, zrobiłem sobie słodko-ostry chłodnik arbuzowy. Wyszło nieźle, więc dla potomności:
Yesterday (August, 7th), Tom Lane committed:
Log Message:
-----------
Recognize functional dependency on primary keys. This allows a table's
other columns to be referenced without listing them in GROUP BY, so long as
the primary key column(s) are listed in GROUP BY.
Eventually we should also allow functional dependency on a UNIQUE constraint
when the columns are marked NOT NULL, but that has to wait until NOT NULL
constraints are represented in pg_constraint, because we need to have
pg_constraint OIDs for all the conditions needed to ensure functional
dependency.
Peter Eisentraut, reviewed by Alex Hunsaker and Tom Lane
On 28th of July, Simon Riggs committed patch which:
Log Message:
-----------
Reduce lock levels of CREATE TRIGGER and some ALTER TABLE, CREATE RULE actions.
Avoid hard-coding lockmode used for many altering DDL commands, allowing easier
future changes of lock levels. Implementation of initial analysis on DDL
sub-commands, so that many lock levels are now at ShareUpdateExclusiveLock or
ShareRowExclusiveLock, allowing certain DDL not to block reads/writes.
First of number of planned changes in this area; additional docs required
when full project complete.
Some guy came to #postgresql today. Described his problem, got additional question, and then … well .. I wouldn’t believe if it didn’t happen to me.
On 25th Robert Haas committed patch which adds first of ‘CREATE IF NOT EXISTS’ commands:
Log Message:
-----------
CREATE TABLE IF NOT EXISTS.
Reviewed by Bernd Helmle.
Let’s imagine simple situation – you have table of objects (each with id), and you want objects 3, 71, 5 and 16. And in that order!
How to do it?
