Re: [GENERAL] Security implications of (plpgsql) functions - Mailing list pgsql-hackers

From Doug McNaught
Subject Re: [GENERAL] Security implications of (plpgsql) functions
Date
Msg-id m3smyzsqon.fsf@varsoon.wireboard.com
Whole thread Raw
In response to Re: [GENERAL] Security implications of (plpgsql) functions  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Joe Conway <mail@joeconway.com> writes:

> Tom Lane wrote:
> > A depth limit for PL-function recursion is perhaps feasible, but I can't
> > say that I care for it a whole lot ... anyone have better ideas?
> >
> 
> Is there any way to recognize infinite recursion by analyzing the
> saved execution tree -- i.e. can we assume that a function that calls
> itself, with the same arguments with which it was called, constitutes
> infinite recursion?

Solved the halting problem lately?  ;)

Someone determined to DoS could probably get around any practical
implementation of your idea, using dummy argument, mutual recursion or
whatever. 

-Doug


pgsql-hackers by date:

Previous
From: Doug McNaught
Date:
Subject: Re: Postgresql and multithreading
Next
From: Tom Lane
Date:
Subject: Re: autocommit vs TRUNCATE et al