Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) - Mailing list pgsql-hackers

On Mon, May 22, 2006 at 10:00:22AM -0500, Jim C. Nasby wrote:
> > T-SQL has statement-level triggers, and they get used a lot (some big apps
> > ONLY put code in triggers). Statement-level triggers are very efficient for
> > maintaining aggregates; the closest PG has are rewrite rules.
>
> Yeah, I wish PostgreSQL had them. I've got clients that could certainly
> make use of them.

What are you referring to that is not supported currently?

CREATE TRIGGER name { BEFORE | AFTER } { event [ OR ... ] }   ON table FOR EACH STATEMENT   EXECUTE PROCEDURE funcname
(arguments ) 

> > For high-end MSSQL shops, a high value is being able to trace and profile
> > (EXPLAIN) every client SQL command from the server side ... with plenty of
> > options for selective trace.
>
> This would also be highly valuable to have in PostgreSQL.

Are we talking EXPLAIN (which is cheap) or EXPLAIN ANALYZE (which is
less so)?

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.