| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Sonam Sharma <sonams1209(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Shared memory error |
| Date: | 2020-06-04 20:16:09 |
| Message-ID: | CA+hUKGJkCH7Q_9qGaZhOMKqG1Q1Hk8qWvkZwehurGKLPvqDQtg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jun 5, 2020 at 1:00 AM Sonam Sharma <sonams1209(at)gmail(dot)com> 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, hmm. When you say "filling", maybe you hit the leaking shm
problem that was fixed in 11.7, that requires messages somewhere in
your log about lack of DSM slots? I don't have an explanation for the
exact the error you're seeing though. It's a bit tricky to speculate
on older releases with so many bug fixes missing though. Please let
us know if you still see the problem after your next scheduled
upgrade.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-06-04 20:24:30 | Re: Monitoring for long running transactions |
| Previous Message | Samuel Smith | 2020-06-04 19:59:51 | Re: Monitoring for long running transactions |