Re: [HACKERS] PSQL commands: \quit_if, \quit_unless - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [HACKERS] PSQL commands: \quit_if, \quit_unless
Date
Msg-id ab39216e-83bb-a910-9c87-ba65a4b601fa@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] PSQL commands: \quit_if, \quit_unless  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 1/13/17 11:22 PM, Tom Lane wrote:
> I wonder what depth of include-file nesting
> psql can support, or whether we'll be able to fix it to optimize tail
> recursion of an include file.  Because somebody will be asking for that
> if this is the toolset you give them.

I think the solution to that is straightforward: tell users that we hope 
to eventually support loops and that in the meantime if you try to work 
around that with recursion you get to keep both pieces when it breaks. 
While not ideal I think that's a lot better than throwing the whole idea 
out because some people will abuse it...
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] Packages: Again
Next
From: Jim Nasby
Date:
Subject: Re: [HACKERS] GSoC 2017