Allan Simon

up

I see two way of supporting it 1. adding the support directly in the lambda layer 2. use https://aws.amazon.com/blogs/compute/using-response-streaming-with-aws-lambda-web-adapter-to-optimize-performance/ ? ( they seems to have example with laravel) for us...

@selfsimilar does it work in the sense "it does not throw an error" or in the sense it's *actually* streamed (i.e it does not get buffered by bref/lambda ) ?

@selfsimilar ok because one year ago when i tried it was also "not throwing errors" (which was good enough for me) , the way I tested it was to add...

to be honest I second @StephaneLeveugle , that number was different with the initial log I had in production. but yes may be not that directly linked to this property,...

Also I can't reproduce it with the image `bref/php-81-fpm-dev`

I've just found this issue https://github.com/php/php-src/issues/9010 so I will propose as here https://github.com/php/php-src/issues/9010#issuecomment-1184680406 a PR to set the limit to the limit of AWS cloudwatch

@mnapoli so the `log_limit` may have been a red herring, my next hypothesis is a bug in Symfony/process i.e some buffer being full causing the process to hang see https://github.com/symfony/symfony/issues/5704#issuecomment-18715686...

@driskell I forgot to repport, but I arrived at the same conclusion as you on your 2 first paragraph, I'm not knowledgeable enough for the 3rd one, I don't know...

I've tested manually on Postgresql 10 (with no support at all of GENERATED column, hence the feature detection code ) , Postgresql 13, 14, 15 For automated test, I've written...