Npgsql...... There is not enough space left in the buffer.
See original GitHub issueThe issue
Working with Npgsql.EntityFrameworkCore.PostgreSQL" Version=“5.0.5.1”, getting below error when try to list of entity data with child entity collection.
Exception message:
System.InvalidOperationException: There is not enough space left in the buffer.
at Npgsql.NpgsqlReadBuffer.ThrowNotSpaceLeft().......
Stack trace:
Further technical details
Npgsql version: 5.0.4 PostgreSQL version: V 13 Operating system: Windows 10 64bit
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
"There is not enough space left in the buffer ...
I've get this same error in Npgsql EFCore 3.1, when I try use a add range inside a transaction. Ex: try{ var listSplited...
Read more >No buffer space available - postgresql
This error message is thrown by PostgreSQL when a Winsock operation returns the error WSAENOBUFS . Microsoft describes the error as: No ......
Read more >Npgsql...... There is not enough space left in the buffer. -
Working with Npgsql.EntityFrameworkCore.PostgreSQL" Version="5.0.5.1", getting below error when try to list of entity data with child entity ...
Read more >Postgres server running out of disk space | Apigee Edge
The steps provided below will help you to determine if you have enough disk space or not and take appropriate action to address...
Read more >Postgres is Out of Disk and How to Recover
If Postgres has run out of disk space, there are a few things to look for. Depending on the server configuration there may...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same issue here, updating from Npgsql.EntityFrameworkCore.PostgreSQL 6.0.6 to 6.0.7 resolved the issue
Closing as no code sample was provided.