Hi Jeff,
Thanks for the reply.
Below are the replies to your queries regarding my issue.
Are you using a custom hashing function or a built-in one?
Answer: I am not using a custom hash function
What is the datatype of the partition key?
Answer: The datatype is bigint.
Has this system been through any pg_upgrade cycles?
Answer: No
Have you tried to reproduce it on your own system?
Answer: Yes, in the system, and all things are fine.
What is your version, hardware, and OS?
Answer: It's the 14 version, and it's an RDS service of AWS, which has a configuration of db.r6g.16xlarge.
Do you have error correcting code RAM?
Answer: It is hosted on the AWS cloud.
Just add up the indexing.
Answer : I was meant to say that the only change i did in table strutute was creation of index.
Hi Team,
While using hash partition i am facing the problem that the data is not going into the proper partition table .
Due to this, records are not visible in the main table when I am searching for a particular record, as it searches only that partition.
Any suggestions on how to overcome this problem and why this happened.
This seems like a bug, or some kind of corruption. But there isn't enough info here to identify what the bug might be. Are you using a custom hashing function, or a built-in one? What is the datatype of the partition key? Has this system been through any pg_upgrade cycles? Have you tried to reproduce it on your own system? What is your version and hardware and OS? Do you have error correcting code RAM?
And in the future, if i truncate the records from the main table and insert them back again, will the shuffling of records happen or not.
Any ideas regarding why this happened?
I don't think there is a way to answer that without first identifying what went wrong in the first place.
Just add up the indexing.
I don't know what that means.
Cheers,
Jeff
-- Have a Good day !!!
Regards
Rohit Sachdeva
