Scott Marlowe wrote:
On Sun, May 3, 2009 at 9:38 AM, Wojtek wrote:
(...)
You could raise notice and then tail the logs as it runs. Or the
other option mentioned of using dblink() works well too.
dblink did the trick, thanks guys!
foo
--
Sent via pgsql-general mailing list (pgsq
On 2009-05-03, Scott Marlowe wrote:
> On Sun, May 3, 2009 at 9:38 AM, Wojtek wrote:
>> Hi,
>>
>> I have a question on transactions/isolation levels/etc...
>> In my PL/pgSQL function main loop goes through inventory list of active
>> devices, for each one executing processing applicable for given
On Sun, May 3, 2009 at 9:38 AM, Wojtek wrote:
> Hi,
>
> I have a question on transactions/isolation levels/etc...
> In my PL/pgSQL function main loop goes through inventory list of active
> devices, for each one executing processing applicable for given device,
> like:
> FOR i in --i is %rowtype
>
Wojtek wrote:
Hi,
I have a question on transactions/isolation levels/etc...
In my PL/pgSQL function main loop goes through inventory list of active
devices, for each one executing processing applicable for given device,
like:
FOR i in --i is %rowtype
select device_id as device_id,
type
Wojtek wrote:
> But... Postgress treats function as single transaction, of course.
> Hence, I'm not able to see any changes in my progress monitoring table
> until my main function is finished and all the statuses are set to 0.
You could use dblink() to insert into your logging table.
David.
--
Hi,
I have a question on transactions/isolation levels/etc...
In my PL/pgSQL function main loop goes through inventory list of active
devices, for each one executing processing applicable for given device,
like:
FOR i in --i is %rowtype
select device_id as device_id,
type as type
from devices_
