On 3/27/24 18:00, Jeff Ross wrote:
On 3/27/24 17:35, Rob Sargent wrote:
On 3/27/24 17:05, Jeff Ross wrote:
On 3/27/24 15:44, Tom Lane wrote:
Perhaps "pinned" in the error message means "open"?
No, it means "pinned" ... but I see that plpython pins the portal
underlying any PLyCursor objec
On 3/27/24 17:35, Rob Sargent wrote:
On 3/27/24 17:05, Jeff Ross wrote:
On 3/27/24 15:44, Tom Lane wrote:
Perhaps "pinned" in the error message means "open"?
No, it means "pinned" ... but I see that plpython pins the portal
underlying any PLyCursor object it creates. Most of our PLs do
th
On 3/27/24 17:41, Adrian Klaver wrote:
On 3/27/24 16:35, Rob Sargent wrote:
On 3/27/24 17:05, Jeff Ross wrote:
On 3/27/24 15:44, Tom Lane wrote:
Perhaps "pinned" in the error message means "open"?
No, it means "pinned" ... but I see that plpython pins the portal
underlying any PLyCursor
On 3/27/24 16:35, Rob Sargent wrote:
On 3/27/24 17:05, Jeff Ross wrote:
On 3/27/24 15:44, Tom Lane wrote:
Perhaps "pinned" in the error message means "open"?
No, it means "pinned" ... but I see that plpython pins the portal
underlying any PLyCursor object it creates. Most of our PLs do
tha
On 3/27/24 17:05, Jeff Ross wrote:
On 3/27/24 15:44, Tom Lane wrote:
Perhaps "pinned" in the error message means "open"?
No, it means "pinned" ... but I see that plpython pins the portal
underlying any PLyCursor object it creates. Most of our PLs do
that too, to prevent a portal from disapp
On 3/27/24 15:44, Tom Lane wrote:
Perhaps "pinned" in the error message means "open"?
No, it means "pinned" ... but I see that plpython pins the portal
underlying any PLyCursor object it creates. Most of our PLs do
that too, to prevent a portal from disappearing under them (e.g.
if you were to
Jeff Ross writes:
> I only use one plpython3u cursor in that function. The plpython docs say:
> "Cursors are automatically disposed of. But if you want to explicitly
> release all resources held by a cursor, use the |close| method. Once
> closed, a cursor cannot be fetched from anymore."
> ht
On 3/20/24 17:04, Tom Lane wrote:
Adrian Klaver writes:
Haven't had a chance to go through this yet. I'm going to say though
that Tom Lane is looking for a shorter generic case that anyone could
run on their system.
Yeah, it's a long way from that trigger function definition to a
working (i.e
On 3/27/24 04:29, Bandi, Venkataramana - Dell Team wrote:
Hi,
As l already mentioned, for this specific node also data is persisting but
sometimes(randomly) data is not persisting.
How do you know which data is not persisting?
As you mentioned our application doesn't have any restrictions
After terminating session file has been updated with new lines.
***content from the previous letter***
***That one unfinished line. Freeze for ~6 hours.***
epoll_wait(4, 0x555d738e4f30, 1, -1) = -1 EINTR (Interrupted system call)
<21328.371590>
--- SIGTERM {si_signo=SIGTERM, si_code=SI_USE
I was able to connect to this process using
strace -T -p `pgrep -n -u ks-postgres -f "ocb.*FETCH"` -o
strace_of_active_session -ff
(the -T flag gives us the time the system call has been running at the end of
each line).
If the session had been hanging active for some time, there was only on
Hi,
As l already mentioned, for this specific node also data is persisting but
sometimes(randomly) data is not persisting.
As you mentioned our application doesn't have any restrictions on OS level and
on network etc.
different OS or OS version, different encoding, different location on the
n
Hi Adrian,
I will check with the customer on below info for that node and will share you.
For instance different OS or OS version, different encoding, different location
on the network, different data it is working, etc.
As I already mentioned we have enabled Postgres SQL debug logs to trace ou
13 matches
Mail list logo
