Re: Huge input lookup exception when trying to create the index for XML data type column in postgreSQL

ere is no other option. I need the other ways to create the index . May be if there are any parameters to change like xmloption etc it would help us to resolve the issue. Thanks, Sai On Fri, 8 Sep, 2023, 1:51 am Tom Lane, wrote: > Erik Wienhold writes: > > On 07/09/2023 21:09 CEST Tom

Huge input lookup exception when trying to create the index for XML data type column in postgreSQL

Hi All, We have one table which is storing XML data with 30k records and stores huge amount of data. We are trying to create the index for this column in the table. But, we’re getting “Huge input Lookup error” during creation of Index. Please check the below command which is used to create the i

Re: postgreSQL UPPER Method is converting the character "µ" into "M"

I added one column with generated always column with UPPER CASE like below:- Alter table table_name t add column data varchar(8000) generated always as (UPPER(t.content)) stored Data column is generated always constraint here This column has many sentences for each row in which some of the chara

Re: postgreSQL UPPER Method is converting the character "µ" into "M"

ta explicitly through UPPER netword like select UPPER('Mass') then I'm getting expected output such as MASS Would request you to please suggest the ideas to resolve this issue. Thanks, Sai Teja On Wed, 6 Sep, 2023, 8:59 pm Francisco Olarte, wrote: > On Wed, 6 Sept 2023 at 16

Re: postgreSQL UPPER Method is converting the character "µ" into "M"

f any alternatives are there to resolve this issue. Thanks, Sai Teja On Wed, 6 Sep, 2023, 7:23 pm Tom Lane, wrote: > Sai Teja writes: > > I am using UPPER document name for converting the text from lower case > into > > upper case. > > But here for the below example >

postgreSQL UPPER Method is converting the character "µ" into "M"

is hosted in Linux Machine which is using Locale_ctype:- en_US_utf.8 Would request you to please suggest any ideas to resolve this issue. It'll would be very helpful and appreciated. Thanks, Sai Teja

Taking too much time to fetch the data from Azure postgreSQL Large objects (pg_largeobjects)

st to please suggest any ideas/solution to resolve this issue. Thanks, Sai

Re: Fatal Error : Invalid Memory alloc request size 1236252631

d retrieve it. Currently It is not happening due to limit of field size set by postgreSQL. Would request to share your insights and suggestions on this to help me for resolving this issue. Thanks & Regards, Sai Teja On Tue, 15 Aug, 2023, 8:53 am Tom Lane, wrote: > Sai Teja writes: >

Re: Fatal Error : Invalid Memory alloc request size 1236252631

. Thanks & Regards, Sai On Tue, 15 Aug, 2023, 8:10 am Sai Teja, wrote: > By default the bytea_output is in hex format. > > On Tue, 15 Aug, 2023, 12:44 am Ron, wrote: > >> Did you *try* changing bytea_output to hex? >> >> On 8/14/23 12:31, Sai Teja wrote: >&

Re: Fatal Error : Invalid Memory alloc request size 1236252631

By default the bytea_output is in hex format. On Tue, 15 Aug, 2023, 12:44 am Ron, wrote: > Did you *try* changing bytea_output to hex? > > On 8/14/23 12:31, Sai Teja wrote: > > I am just running select query to fetch the result > Query : select id, content_data, name from ta

Re: Fatal Error : Invalid Memory alloc request size 1236252631

ry is being called in java as well So, I don't think java could be the issue as I can able to successfully insert the data. But, only the problem is with fetching the data that too only specific rows which are having huge volume of data. Thanks, Sai On Mon, 14 Aug, 2023, 10:55 pm Rob Sargent, wr

Re: Fatal Error : Invalid Memory alloc request size 1236252631

that particular row. Would be appreciated if anyone share the insights. Thanks, Sai On Mon, 14 Aug, 2023, 5:21 pm Sai Teja, wrote: > Hi Andreas, > > Thank you for the reply! > > Currently it is Hex by default. If I change to escape is there any > possibility to fetch the

Fatal Error : Invalid Memory alloc request size 1236252631

solve this issue. Thanks & Regards, Sai Teja

Re: org.postgresql.util.PSQLException: ERROR: invalid XML content. Huge Input lookup

Best Regards, Sai Teja On Fri, 4 Aug, 2023, 8:03 am Ron, wrote: > On 8/3/23 21:22, Sai Teja wrote: > > Hi team, > > I am trying to migrate the data from db2 to postgreSQL in which one of the > table is having XML data. > For one of the file (13MB) I'm facing an err

org.postgresql.util.PSQLException: ERROR: invalid XML content. Huge Input lookup

o migrate into azure postgreSQL (Linux OS, located in Germany) facing an issue. I request you to please look into this and help me to resolve this error. Please let me know if any queries. Looking forward for the resolution. Thanks & regards, Sai Teja

Reg: User creation script/List of privileges

Hi Experts, I am looking for a query or possibility to generate all the privileges a user/role has. I need this to create a user/role from one database to another with exact same privileges. Kindly, share the query or way to proceed further. Thanks & Regards, Sai.

request to support "conflict on(col1 or col2) do update xxx" feature

I think this feature is a very common requirement. For example. I created a table, which username and email columns are unique separately CREATE TABLE test ( usernameVARCHAR(255) NOT NULL UNIQUE, email VARCHAR(255) NOT NULL UNIQUE, status VARCHAR(127) ); I want to do