Skip site navigation (1) Skip section navigation (2)

Re: Actions requiring commit

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Lee <Lee(at)jamtoday(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Actions requiring commit
Date: 2010-02-15 01:34:13
Message-ID: 407d949e1002141734g308cd938n49e59aaf55bf4d38@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-novice
On Sun, Feb 14, 2010 at 7:07 PM, Lee <Lee(at)jamtoday(dot)com> wrote:
> What's the postgres story? If I write to a native operating system file,
> (and don't commit), does the output appear immediately (no counting internal
> small delay) ?
>
> What about issuing a "system" (shell) comnmand? Causing an signal,  (er
> "Notify" in postrges land, I guess) , putting something on a queue via PGQ
> or similar
> tool?

In Postgres anything that Postgres manages itself only happens at
commit. So aside from table modifications and schema changes NOTIFY
only takes place at commit. But if you have a pl language like plperl
or plsh write to a file that's outside Postgres's sphere of influence
and it will happen right away.

I'm not familiar with PGQ, I'm not sure which tack it takes. Its
documentation should have an answer though.

-- 
greg

In response to

Responses

pgsql-novice by date

Next:From: Lee HorowitzDate: 2010-02-15 01:50:31
Subject: Re: Actions requiring commit
Previous:From: bill houseDate: 2010-02-14 22:17:51
Subject: Function

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group