Re: Database crash when creating raster_in function

2024-03-18 Thread Nikhil Shetty
Hi Regina,

I checked the code that we used to build 3.3.5 packages and you are right
the fix is already present  but not sure why we are still getting the error
on PG15.

I will debug and get back to you.

Thanks,
Nikhil

On Mon, Mar 18, 2024 at 1:55 PM Regina Obe  wrote:

> Most of that fix should already be in the PG15 3.3.5 except for the parts
> that have PG16 guards, cause they wouldn’t work in PG15 or lower.
>
> So If you find trying to reapply to 3.3.5 works I’d be surprised and be
> interested in which portion of patch you applied.
>
>
>
>
>
>
>
> *From:* Nikhil Shetty 
> *Sent:* Sunday, March 17, 2024 9:49 AM
> *To:* Regina Obe 
> *Cc:* PostGIS Users Discussion 
> *Subject:* Re: Database crash when creating raster_in function
>
>
>
> I am  are using raster extension
>
>
>
> The creation of raster_in function breaks on PG15 as well, JFYI, I have
> created package for 3.3.5 on rhel7(this is not available in Postgres repo)
>
>
>
> Will the fix given in
>
>  https://trac.osgeo.org/postgis/ticket/5277
>
>  solve the issue? if yes, I can add the same fix and create new rpms for
> 3.3.5 on rhel7
>
>
>
> Thanks,
>
> Nikhil
>
>
>
> On Sun, 17 Mar 2024 at 10:07, Regina Obe  wrote:
>
> Yap that was fixed in PostGIS 3.3.3.
>
> The change there was to support a change in PG16, so you shouldn’t need it
> for upgrading from PG13 to PG15.
>
>
>
> Are you using postgis_raster or you just have it installed?
>
>
>
> If you don’t need postgis_raster, I would suggest uninstalling it before
> upgrading.
>
>
>
> *From:* Nikhil Shetty 
> *Sent:* Saturday, March 16, 2024 10:55 AM
> *To:* PostGIS Users Discussion 
> *Subject:* Database crash when creating raster_in function
>
>
>
> Hi Team,
>
>
>
> I am trying to upgrade the postgres database from PG13 to PG15. pg_upgrade
> is crashing with below error when creating the raster_in function
>
>
>
> pg_restore: creating FUNCTION "public.raster_in("cstring")"
> pg_restore: while PROCESSING TOC:
> pg_restore: from TOC entry 394; 1255 16439 FUNCTION raster_in("cstring")
> postgres
> pg_restore: error: could not execute query: server closed the connection
> unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> Command was: CREATE FUNCTION "public"."raster_in"("cstring") RETURNS
> "public"."raster"
> LANGUAGE "c" IMMUTABLE STRICT PARALLEL SAFE
> AS '$libdir/postgis_raster-3', 'RASTER_in';
>
>
>
>
>
> PostGIS version : *3.3.5*
>
>
>
> This looks similar to the issue mentioned in
> https://trac.osgeo.org/postgis/ticket/5277. Is this fixed in 3.3.5 ?
>
>
>
> Thanks,
>
> Nikhil
>
>


RE: Database crash when creating raster_in function

2024-03-18 Thread Regina Obe
Most of that fix should already be in the PG15 3.3.5 except for the parts that 
have PG16 guards, cause they wouldn’t work in PG15 or lower.

So If you find trying to reapply to 3.3.5 works I’d be surprised and be 
interested in which portion of patch you applied.

 

 

 

From: Nikhil Shetty  
Sent: Sunday, March 17, 2024 9:49 AM
To: Regina Obe 
Cc: PostGIS Users Discussion 
Subject: Re: Database crash when creating raster_in function

 

I am  are using raster extension 

 

The creation of raster_in function breaks on PG15 as well, JFYI, I have created 
package for 3.3.5 on rhel7(this is not available in Postgres repo)

 

Will the fix given in 

  <https://trac.osgeo.org/postgis/ticket/5277> 
https://trac.osgeo.org/postgis/ticket/5277

 solve the issue? if yes, I can add the same fix and create new rpms for 3.3.5 
on rhel7

 

Thanks,

Nikhil

 

On Sun, 17 Mar 2024 at 10:07, Regina Obe mailto:l...@pcorp.us> 
> wrote:

Yap that was fixed in PostGIS 3.3.3.

The change there was to support a change in PG16, so you shouldn’t need it for 
upgrading from PG13 to PG15.

 

Are you using postgis_raster or you just have it installed?

 

If you don’t need postgis_raster, I would suggest uninstalling it before 
upgrading. 

 

From: Nikhil Shetty mailto:nikhil.db...@gmail.com> > 
Sent: Saturday, March 16, 2024 10:55 AM
To: PostGIS Users Discussion mailto:postgis-users@lists.osgeo.org> >
Subject: Database crash when creating raster_in function

 

Hi Team,

 

I am trying to upgrade the postgres database from PG13 to PG15. pg_upgrade is 
crashing with below error when creating the raster_in function

 

pg_restore: creating FUNCTION "public.raster_in("cstring")"
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 394; 1255 16439 FUNCTION raster_in("cstring") 
postgres
pg_restore: error: could not execute query: server closed the connection 
unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
Command was: CREATE FUNCTION "public"."raster_in"("cstring") RETURNS 
"public"."raster"
LANGUAGE "c" IMMUTABLE STRICT PARALLEL SAFE
AS '$libdir/postgis_raster-3', 'RASTER_in';

 

 

PostGIS version : 3.3.5

 

This looks similar to the issue mentioned in 
https://trac.osgeo.org/postgis/ticket/5277. Is this fixed in 3.3.5 ?

 

Thanks,

Nikhil



Re: Database crash when creating raster_in function

2024-03-17 Thread Nikhil Shetty
I am  are using raster extension

The creation of raster_in function breaks on PG15 as well, JFYI, I have
created package for 3.3.5 on rhel7(this is not available in Postgres repo)

Will the fix given in
 https://trac.osgeo.org/postgis/ticket/5277
 solve the issue? if yes, I can add the same fix and create new rpms for
3.3.5 on rhel7

Thanks,
Nikhil

On Sun, 17 Mar 2024 at 10:07, Regina Obe  wrote:

> Yap that was fixed in PostGIS 3.3.3.
>
> The change there was to support a change in PG16, so you shouldn’t need it
> for upgrading from PG13 to PG15.
>
>
>
> Are you using postgis_raster or you just have it installed?
>
>
>
> If you don’t need postgis_raster, I would suggest uninstalling it before
> upgrading.
>
>
>
> *From:* Nikhil Shetty 
> *Sent:* Saturday, March 16, 2024 10:55 AM
> *To:* PostGIS Users Discussion 
> *Subject:* Database crash when creating raster_in function
>
>
>
> Hi Team,
>
>
>
> I am trying to upgrade the postgres database from PG13 to PG15. pg_upgrade
> is crashing with below error when creating the raster_in function
>
>
>
> pg_restore: creating FUNCTION "public.raster_in("cstring")"
> pg_restore: while PROCESSING TOC:
> pg_restore: from TOC entry 394; 1255 16439 FUNCTION raster_in("cstring")
> postgres
> pg_restore: error: could not execute query: server closed the connection
> unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> Command was: CREATE FUNCTION "public"."raster_in"("cstring") RETURNS
> "public"."raster"
> LANGUAGE "c" IMMUTABLE STRICT PARALLEL SAFE
> AS '$libdir/postgis_raster-3', 'RASTER_in';
>
>
>
>
>
> PostGIS version : *3.3.5*
>
>
>
> This looks similar to the issue mentioned in
> https://trac.osgeo.org/postgis/ticket/5277. Is this fixed in 3.3.5 ?
>
>
>
> Thanks,
>
> Nikhil
>


RE: Database crash when creating raster_in function

2024-03-16 Thread Regina Obe
Yap that was fixed in PostGIS 3.3.3.

The change there was to support a change in PG16, so you shouldn’t need it for 
upgrading from PG13 to PG15.

 

Are you using postgis_raster or you just have it installed?

 

If you don’t need postgis_raster, I would suggest uninstalling it before 
upgrading. 

 

From: Nikhil Shetty  
Sent: Saturday, March 16, 2024 10:55 AM
To: PostGIS Users Discussion 
Subject: Database crash when creating raster_in function

 

Hi Team,

 

I am trying to upgrade the postgres database from PG13 to PG15. pg_upgrade is 
crashing with below error when creating the raster_in function

 

pg_restore: creating FUNCTION "public.raster_in("cstring")"
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 394; 1255 16439 FUNCTION raster_in("cstring") 
postgres
pg_restore: error: could not execute query: server closed the connection 
unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
Command was: CREATE FUNCTION "public"."raster_in"("cstring") RETURNS 
"public"."raster"
LANGUAGE "c" IMMUTABLE STRICT PARALLEL SAFE
AS '$libdir/postgis_raster-3', 'RASTER_in';

 

 

PostGIS version : 3.3.5

 

This looks similar to the issue mentioned in 
https://trac.osgeo.org/postgis/ticket/5277. Is this fixed in 3.3.5 ?

 

Thanks,

Nikhil