Re: Having a plpgsql function return multiple rows that indicate its progress in a cursor like fashion

From: Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Having a plpgsql function return multiple rows that indicate its progress in a cursor like fashion
Date: 2010-02-16 23:39:18
Message-ID: db471ace1002161539i4d0f55edn94c6f1db21780197@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>> Aren't my requirements sufficiently common to justify developing a
>> mechanism to report progress back to client applications during batch
>> operations and the like?
>
> Have you experimented with RAISE NOTICE?  Using it this way is a bit of
> a hack maybe, but I think you are entirely unaware of what would be
> involved in producing something that's less of a hack.

That assessment is accurate. Should I take it that you aren't
particularly interested in pursuing something like this at present?

I'll see what I can come up with by playing with RAISE NOTICE

Thanks,
Peter Geoghegan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2010-02-17 00:00:38 Re: Source RPMs for PostgreSQL 7.4.27 on RHEL4
Previous Message Justin Pasher 2010-02-16 23:13:22 Source RPMs for PostgreSQL 7.4.27 on RHEL4