From: David Garamond <davidgaramond@gmail.com>
To: Richard Huxton <dev@archonet.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: autoupdating mtime column
Date: Sat, 5 Aug 2006 08:27:52 +0700
Message-ID: <7c33d060608041827y8835d82q85772f56eced621f@mail.gmail.com> (raw)
In-Reply-To: <44D38F8A.8040302@archonet.com>
References: <7c33d060608040516n799af906sf74e1c645a47caff@mail.gmail.com>
<44D34242.6000901@archonet.com>
<7c33d060608040811s6dcaa3abia137188076a76781@mail.gmail.com>
<29505.1154707823@sss.pgh.pa.us>
<7c33d060608041036k59056658o5acd68df36d0bbb6@mail.gmail.com>
<44D38F8A.8040302@archonet.com>
On 8/5/06, Richard Huxton <dev@archonet.com> wrote:
>
> >> have a real use-case for suppressing mtime updates?
> > Syncing tables between databases (a la "rsync --times"). Btw, I'm
> > considering temporarily disabling the update_times() trigger when
> sync-ing.
>
> I'd consider running the sync as a different (privileged) user and
> checking the current user in the trigger. Ordinary users always get
> now(), privileged users always get what they provide (and they are
> forced to provide some value). Does what you want and adds a safety
> catch too.
>
> Alternatively, you could do something similar with views.
>
That's a nice idea indeed. Thanks!
--
dave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: davidgaramond@gmail.com, dev@archonet.com, tgl@sss.pgh.pa.us
Subject: Re: autoupdating mtime column
In-Reply-To: <7c33d060608041827y8835d82q85772f56eced621f@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox