On Fri, Jun 5, 2020 at 1:00 AM Sonam Sharma wrote:
> The dynamic_shared_memory_type was set to POSIX . Because of this it was
> using tmpfs /dev/shm. When the query was running I saw the file system was
> filling. So I extended the file system and luckily the query worked for that
> time
Oh,
The dynamic_shared_memory_type was set to POSIX . Because of this it was
using tmpfs /dev/shm. When the query was running I saw the file system was
filling. So I extended the file system and luckily the query worked for
that time
On Thu, Jun 4, 2020, 5:12 PM Thomas Munro wrote:
> >> Do you see
>> Do you see any other errors around this one, in the PostgreSQL logs?
> No , only this is the error from db and jdbc end .. and queries are failing
If you need a workaround right now you could always set
max_parallel_workers_per_gather=0 so that it doesn't try to use
parallel query. That could
On Thu, Jun 4, 2020 at 6:18 AM Sonam Sharma wrote:
>>> 1) Postgres version : 11.2
FYI This is missing over a year's worth of bugfixes. That said, I
don't know of anything fixed that has this symptom.
>>> 4) Is this only with one query and if so what is it doing? : No , few
>>> queries work, fe
Hi,
If the dynamic shared memory segment type is POSIX then *dynamic shared
memory control segment in your case it is **PostgreSQL.1511679208* is
stored in */dev/shm*
The file you mentioned will be created at the time of PostgreSQL startup
and cleared automatically on successful shutdown.
Compl
Can someone please help on this
On Wed, Jun 3, 2020, 11:27 PM Sonam Sharma wrote:
> I have set the dynamic_shared_memory_type to none which was set as POSIX.
> For now we are not seeing the error... Can someone please explain what is
> the impact of setting it as none .
>
> On Wed, Jun 3, 2020,
Updated jdbc version also
On Wed, Jun 3, 2020, 11:46 PM Sonam Sharma wrote:
>
>
> On Wed, Jun 3, 2020, 11:29 PM Adrian Klaver
> wrote:
>
>> On 6/3/20 7:58 AM, Sonam Sharma wrote:
>> > Hi Team,
>> >
>> > Getting below error when any query is running from jdbc side :
>> >
>> > Error : could not o
On Wed, Jun 3, 2020, 11:29 PM Adrian Klaver
wrote:
> On 6/3/20 7:58 AM, Sonam Sharma wrote:
> > Hi Team,
> >
> > Getting below error when any query is running from jdbc side :
> >
> > Error : could not open memory segment "/PostgreSQL.1511679208" : No such
> > file or directory
> >
> > Yesterday
On 6/3/20 7:58 AM, Sonam Sharma wrote:
Hi Team,
Getting below error when any query is running from jdbc side :
Error : could not open memory segment "/PostgreSQL.1511679208" : No such
file or directory
Yesterday I have extended the /dev/shm filesystem and the query ran. But
today again the
I have set the dynamic_shared_memory_type to none which was set as POSIX.
For now we are not seeing the error... Can someone please explain what is
the impact of setting it as none .
On Wed, Jun 3, 2020, 8:28 PM Sonam Sharma wrote:
> Hi Team,
>
> Getting below error when any query is running fro
10 matches
Mail list logo
