The convention here is to inline post replies while trimming quoted content to only that which is being replied.
On Sunday, February 22, 2026, Alexandre Felipe <[email protected]> wrote: > The problem I was trying to solve was the total lack of configurability. > What do you think needs configuring and why? > > > Most/all of what you’ve decided to allow to be ignored has no > variability based on setting values or environment - and likely would be > stuff we wouldn’t want to be optional. > > Now that you can see why my approach wouldn't work, could you suggest an > improvement on that? maybe different directives? > I haven’t given it much thought and am just fine with the status quo. But I gave a couple of quick thoughts you may do with as you please. > If those tests are impossible to fix in regress/sql, should they be > promoted to TAP? > This approach, figuring out a way to run a set of tests under a specific non-default configuration, seems more likely to be taken in. But it seems to me the odds are going to be low that anyone contributes new tests to the file over the course of regular development. > > Maybe the tests are easy to fix, e.g. INSERT INTO toasttest values > (repeat('1234567890',300)); expects toasting, instead of 300 it should use > something based on current_setting(...), or set the minimum toast length on > the table. > > In my regression it was just 30 failures, bad but not so bad. > Then patch in the more robust query format that retains the intent of the test. Any other solution is going to quickly hit up against human attention limitations. David J.
