Re: Print warning when I execute my own extension function - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Print warning when I execute my own extension function
Date
Msg-id 20220220102904.is363jnajvj7kct5@jrouhaud
Whole thread Raw
In response to Print warning when I execute my own extension function  (Dong Wook Lee <sh95119@gmail.com>)
Responses Re: Print warning when I execute my own extension function
List pgsql-hackers
Hi,

On Sun, Feb 20, 2022 at 07:23:56PM +0900, Dong Wook Lee wrote:
> Hi hackers,
> I've read in this blog (
> http://big-elephants.com/2015-10/writing-postgres-extensions-part-i/)
> and I wrote an extension about base36_encode with c code
> but when I executed a query like this below I got a warning below.
>
> ```
> postgres=# SELECT base36_encode(123);
> WARNING:  problem in alloc set ExprContext: detected write past chunk end
> in block 0x55fb75334d40, chunk 0x55fb75334d68
> WARNING:  problem in alloc set ExprContext: detected write past chunk end
> in block 0x55fb75334d40, chunk 0x55fb75334d68
>  base36_encode
> ---------------
>  3f
> (1 row)
> ```
>
> I don't know what this warning means and how I can fix it.

It means that you have some problem in your memory allocation.  You can refer
to src/backend/utils/mmgr/aset.c for more details on those safety checks.



pgsql-hackers by date:

Previous
From: Dong Wook Lee
Date:
Subject: Print warning when I execute my own extension function
Next
From: Ranier Vilela
Date:
Subject: Uniforms the errors msgs at tuplestore paths