Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aY0jN-0001ZE-91 for pgsql-general@arkaria.postgresql.org; Tue, 23 Feb 2016 00:21:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aY0jM-0003o9-9p for pgsql-general@arkaria.postgresql.org; Tue, 23 Feb 2016 00:21:32 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aY0h5-00015k-Bj for pgsql-general@postgresql.org; Tue, 23 Feb 2016 00:19:11 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aY0h2-0005VH-Fm for pgsql-general@postgresql.org; Tue, 23 Feb 2016 00:19:10 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 78C7B20A32 for ; Mon, 22 Feb 2016 19:19:07 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Mon, 22 Feb 2016 19:19:07 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=eY8trCNvC+XcTMxxsAIMC7JVjCw=; b=ZLP9BV j4XFlDjFtzgot6rMuBRmipl+MKnXc7Fv5DJwsJS1dZiYwAcGPKAqYXuDSqDh9hrW STZ9XCKPag3z5W1GvpxHmVpLPZoiZgkNWg6CZNYE/Lemocl6Urr90trEapen7s6m bDYV7N28UpISwup+ss7YUozxKtJNX2mD/52jc= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=eY8trCNvC+XcTMx xsAIMC7JVjCw=; b=L9OllRfVzHpV0BnIBNH06EPHjKSnHbPNt9HXNbS6YG94XoO yt9dXJU3qXYCk/Lv3F9tFAw4B9EecGFk7I78/wuLlGexVU345zyqqheNQ1NDSTZL aADESfwgvD36OOtI17av4l5bE4IysvHB6W5FUwI4ODqIkdApquOKbGk0dGwk= X-Sasl-enc: HWqhIHhhUExHPaYiSsYpuGtnBnMXUrJxLgwEUVK9val3 1456186747 Received: from killi.site (c-73-225-242-52.hsd1.wa.comcast.net [73.225.242.52]) by mail.messagingengine.com (Postfix) with ESMTPA id A356F6800AF; Mon, 22 Feb 2016 19:19:06 -0500 (EST) Subject: Re: Get the date of creation of objects in the database To: "Edson F. Lidorio" , Melvin Davidson , Zlatko Asenov References: <56CB84F7.20803@openmailbox.org> <56cb8920.c74fc20a.c69fa.5153@mx.google.com> <56CB98AA.8040408@openmailbox.org> Cc: "David G. Johnston" , pgsql-general From: Adrian Klaver Message-ID: <56CBA579.6040502@aklaver.com> Date: Mon, 22 Feb 2016 16:19:05 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56CB98AA.8040408@openmailbox.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On 02/22/2016 03:24 PM, Edson F. Lidorio wrote: > > > + 1 > > Listen11similar discussionat [1] > > [1] > http://pgsql-hackers.postgresql.narkive.com/TQSHWw1l/proposal-store-timestamptz-of-database-creation-on-pg-database Where the above leads to is implementing a version control system inside the database. Not necessarily a bad idea, but something I personally see as better handled by dedicated version control software. Myself, I use sqitch(http://sqitch.org/) in combination with Mercurial to keep track of object creation and changes. Being independent of the database it handles dealing with multiple instances(think dev, testing, production) easier. -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general