Thank you Adrian.
We replicated the issue with OS upgrade.
On Tue, 26 Nov, 2024, 11:06 am Adrian Klaver,
wrote:
> On 11/25/24 19:07, shashidhar Reddy wrote:
> > Hi Adrian,
> >
> > Thank you for your response.
> >
> > I don't think index corrupted as
Thank you Tom!
The issue is with OS upgrade we could able replicate it.
On Mon, 25 Nov, 2024, 9:32 pm Tom Lane, wrote:
> shashidhar Reddy writes:
> > The issue is a unique key constraint with two columns one is character
> > another is integer. At some point the unique key di
drian Klaver,
wrote:
> On 11/25/24 00:44, shashidhar Reddy wrote:
> > Hi Ajit,
> >
> > Thank you for your reply!
> >
> > The result of the query is same across all servers and yes streaming
> > replication does not have any issue but the question is how did
> &
; happen in asynchronous, log shipping or streaming replication. In logical
> replication it may create problem.
>
> On Mon, Nov 25, 2024 at 12:01 PM shashidhar Reddy <
> shashidharreddy...@gmail.com> wrote:
>
>> Hello,
>>
>> We have postgresql servers with PostgreSQ
Hello,
We have postgresql servers with PostgreSQL 13.10 on Ubuntu release 22.04.
The issue is a unique key constraint with two columns one is character
another is integer. At some point the unique key did not work as I see
duplicate values with these two columns combination and it happened on
m
t; > On 11/3/23 10:40 AM, shashidhar Reddy wrote:
> >
> > Hello All,
> >
> > I have a Postgresql function scheduled to run on the database, some
> tines
> > it is taking too long than usual time, is it possible to get the
> execution
> >
Thank you Adrian fir the reply, I am looking for something like complete
execution plan of the function just like EXPLAIN does.
On Fri, 3 Nov, 2023, 11:15 pm Adrian Klaver,
wrote:
>
> On 11/3/23 10:44 AM, Adrian Klaver wrote:
>
>
> On 11/3/23 10:40 AM, shashidhar Reddy wrote
Hello All,
I have a Postgresql function scheduled to run on the database, some tines
it is taking too long than usual time, is it possible to get the execution
plan of this function or any other way to troubleshoot
Thank you Adrian! I will apply the patch and see.
On Tue, 26 Sept, 2023, 12:53 am Adrian Klaver,
wrote:
> On 9/25/23 11:55, shashidhar Reddy wrote:
> > Thank you Erik,
> >
> > Not all queries are truncated at same size,different queries different
> > sizes but all 1
Thank you Erik,
Not all queries are truncated at same size,different queries different
sizes but all 11.5 servers are behaving in same manner.
On Mon, 25 Sept, 2023, 5:33 pm Erik Wienhold, wrote:
> On 2023-09-25 16:54 +0530, shashidhar Reddy wrote:
> > We are using postgres 11.5 on
Hi Laurenz,
Iog is also showing few lines that is incomplete statement.
On Mon, 25 Sept, 2023, 5:05 pm Laurenz Albe,
wrote:
> On Mon, 2023-09-25 at 16:54 +0530, shashidhar Reddy wrote:
> > We are using postgres 11.5 on Ubuntu we have enabled logging and set
> > log_statements to
Hello
We are using postgres 11.5 on Ubuntu we have enabled logging and set
log_statements to all but when I checked the statements in the logs I can
see only first few lines of the query and also when I check in pgadmin for
current queries I could see only few lines. Some one please help me to get
Both shows different versions as 13 shows version 13.10 and 12 shows 12.14
On Tue, 21 Mar, 2023, 8:09 pm Adrian Klaver,
wrote:
> On 3/21/23 03:29, shashidhar Reddy wrote:
> > Actually I was using the below command to check the compatibility, it
> > worked without any issue with
hns...@gmail.com <
> david.g.johns...@gmail.com>:
>
> On Sat, Mar 18, 2023 at 7:27PM shashidhar Reddy <
> shashidharreddy...@gmail.com> wrote:
>
> Can someone please help me with this?
>
>
>
> You haven't given others enough information to help
Can someone please help me with this?
On Sun, 19 Mar, 2023, 2:54 am shashidhar Reddy, <
shashidharreddy...@gmail.com> wrote:
> and adding to this the following is also showing in the error, we tried
> changing the file permissions but still no luck
> FATAL: could not load p
and adding to this the following is also showing in the error, we tried
changing the file permissions but still no luck
FATAL: could not load private key file
"/etc/ssl/private/ssl-cert-snakeoil.key": key values mismatch
On Sun, Mar 19, 2023 at 2:09 AM shashidhar Reddy <
sh
Hello,
I am in a process of upgrading postgresql from version 12 to 13 using
pg_upgrdrade but I am getting error stating
FATAL: database files are incompatible with server
DETAIL: The data directory was initialized by PostgreSQL version 13
, which is not compatible with this version 12.14 (Ub
On Tue, 6 Dec, 2022, 4:17 pm Pavel Stehule, wrote:
> Hi
>
> for record - the problem was probably in using plpgsql_check together with
> PL debugger (plugin_debugger). Both extensions use the PLpgSQL DBG API, but
> this API is not designed to be used by more extensions. plpgsql_check has
> implem
l Stehule
> napsal:
>
>>
>>
>> út 29. 11. 2022 v 16:37 odesílatel shashidhar Reddy <
>> shashidharreddy...@gmail.com> napsal:
>>
>>> Plogsql check version is 2.2 and one more finding is before calling the
>>> function if we drop and recreat
Is there any way to get the older version 1.1 of plpgsql_check to install
it?
On Mon, 5 Dec, 2022, 1:36 pm Pavel Stehule, wrote:
>
>
> po 5. 12. 2022 v 8:42 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com> napsal:
>
>> Pavel,
>>
>> Below is
Pavel,
Below is the back trace result
libffi6-dbg libgcc1-dbg libkrb5-dbg libstdc++6-8-dbg libxml2-dbg
postgresql-13-dbgsym postgresql-13-pldeb
ugger-dbgsym zlib1g-dbg
On Mon, Dec 5, 2022 at 11:28 AM Pavel Stehule
wrote:
> Hi
>
>
> po 5. 12. 2022 v 6:49 odesílatel shas
Pavel,
Where can I get list-dbgsym-packages.sh script?
On Wed, Nov 30, 2022 at 10:04 AM Pavel Stehule
wrote:
>
>
> st 30. 11. 2022 v 5:28 odesílatel Pavel Stehule
> napsal:
>
>>
>>
>> st 30. 11. 2022 v 1:38 odesílatel shashidhar Reddy <
>> shashidha
I have tried updating after upgrade but that wasn't working, so I have
dropped and recreated the extension.
Now it is crashing every time when we call the function.
On Tue, 29 Nov, 2022, 9:58 pm Pavel Stehule,
wrote:
>
>
> út 29. 11. 2022 v 16:37 odesílatel shashidhar Reddy <
Plogsql check version is 2.2 and one more finding is before calling the
function if we drop and recreate the plpgsql_check extension there is no
issue, but each time we can't drop and create.
On Tue, 29 Nov, 2022, 7:19 pm shashidhar Reddy, <
shashidharreddy...@gmail.com> wrote:
&g
Hello Pavel,
This is the function causing the issue on all servers, and also i noticed
when I use *plpgsql_check_function *in any function I am facing the same
issue.
On Tue, Nov 29, 2022 at 6:43 PM Pavel Stehule
wrote:
> Hi
>
>
> út 29. 11. 2022 v 13:49 odesílatel shas
Hello,
Recently we have upgraded postgres from version 12 to 13 and upgraded
plpgsql_check
to the latest version but after upgrade when calling the below function
causing postgres restart .
CREATE OR REPLACE FUNCTION pro.po_check(
)
RETURNS void
LANGUAGE 'plpgsql'
COST 100
VOLATIL
Pavel,
I just dropped the extension, thats where I got the second error.
Looks like when any plpgsql functions runs it us looking for plpgsql_check.
On Thu, 17 Nov, 2022, 7:28 pm Pavel Stehule,
wrote:
>
>
> čt 17. 11. 2022 v 13:32 odesílatel shashidhar Reddy <
> shashidharred
function plpgsql_check_function(oid) does not
exist
LINE 1: SELECT p.oid, n.nspname, p.proname, plpgsql_check_function(p...
^
On Thu, Nov 17, 2022 at 11:52 AM shashidhar Reddy <
shashidharreddy...@gmail.com> wrote:
> Ok, I will check.
>
> On Th
Ok, I will check.
On Thu, 17 Nov, 2022, 11:35 am Pavel Stehule,
wrote:
>
>
> čt 17. 11. 2022 v 6:55 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com> napsal:
>
>> Show plpgsql_check.mode gives an error as unrecognized configuration
>> parameter.
Show plpgsql_check.mode gives an error as unrecognized configuration
parameter.
We use plprofiler
On Thu, 17 Nov, 2022, 10:55 am Pavel Stehule,
wrote:
>
>
> čt 17. 11. 2022 v 6:18 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com> napsal:
>
>> Pavel,
>
Pavel,
Plpgsql_check configured under postures 13 lib.
If it us not enabled default how can I do it?
On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule,
wrote:
>
>
> st 16. 11. 2022 v 19:52 odesílatel Tom Lane napsal:
>
>> Pavel Stehule writes:
>> > st 16. 11. 2022 v
Extension version is 2.2. Is anything need to be done? To fix this issue?
On Wed, 16 Nov, 2022, 10:06 pm Tom Lane, wrote:
> shashidhar Reddy writes:
> > I could see an error in syslogs, I am not sure what it means.
> > kernel: [93631.415790] postgres[86383]: se
I could see an error in syslogs, I am not sure what it means.
kernel: [93631.415790] postgres[86383]: segfault at 80 ip 7f07f3e3eefd
sp 7fffcf1db500 error 4 in plpgsql_check.so[7f07f3e2e000+34000]
On Wed, Nov 16, 2022 at 9:36 PM shashidhar Reddy <
shashidharreddy...@gmail.com>
Tom,
I have upgraded them to latest version.
I also used pg_upgrade check before upgrading the postures from 12 to 13.
On Wed, 16 Nov, 2022, 9:32 pm Tom Lane, wrote:
> shashidhar Reddy writes:
> > We have extensions like plpgsql_check and plprofiler.
>
> Hmm. My bet is th
e-pdf-splitflag.xml)
2022-11-16 02:28:08,965 ERROR XmlImport#processInvoice - ERROR:
unrecognized node type: 350
On Wed, Nov 16, 2022 at 7:57 PM Tom Lane wrote:
> shashidhar Reddy writes:
> > We have upgraded postgresql from version 12 to 13.8 and after that
> > facing unrecognized
>
We are using 42.2.21 jdbc version
On Wed, 16 Nov, 2022, 6:26 pm Daniel Gustafsson, wrote:
> > On 16 Nov 2022, at 09:23, shashidhar Reddy
> wrote:
>
> > We have upgraded postgresql from version 12 to 13.8 and after that
> facing unrecognized node type: 350, what could be t
Any help on this?
On Wed, 16 Nov, 2022, 1:53 pm shashidhar Reddy, <
shashidharreddy...@gmail.com> wrote:
> Hello,
>
> We have upgraded postgresql from version 12 to 13.8 and after that facing
> unrecognized
> node type: 350, what could be the issue?
>
> 2022-11-1
Hello,
We have upgraded postgresql from version 12 to 13.8 and after that
facing unrecognized
node type: 350, what could be the issue?
2022-11-16 02:28:08,957 DEBUG Logger#insert - 2022-11-16-02:28:08 -
ERROR - 2022-11-16-02:28:08 - org.postgresql.util.PSQLException:
ERROR: unrecognized node type
Thank you Guillaume!
On Fri, 4 Nov, 2022, 12:49 pm Guillaume Lelarge,
wrote:
> Hi,
>
> Le ven. 4 nov. 2022 à 07:12, shashidhar Reddy <
> shashidharreddy...@gmail.com> a écrit :
>
>> Hello,
>>
>> I am using postgres version 11, in the process of upgrade
Hello,
I am using postgres version 11, in the process of upgrade using pg_upgrade
I am trying to run checksums on version 11 but getting error
pg_verify_checksums: data checksums are not enabled in cluster
when trying to enable /pg_verify_checksums: unrecognized option '--enable'
I need help on
Thank you Julien!
On Thu, Nov 3, 2022 at 12:52 PM Julien Rouhaud wrote:
> On Thu, Nov 03, 2022 at 12:38:53PM +0530, shashidhar Reddy wrote:
> > Hello Julien,
> >
> > Actually production databases are on version 13.4 and the team needs the
> > same version to test some
Hello Julien,
Actually production databases are on version 13.4 and the team needs the
same version to test something on it, is there a way to install the same
version?
On Thu, Nov 3, 2022 at 12:29 PM Julien Rouhaud wrote:
> Hi,
>
> On Thu, Nov 03, 2022 at 12:18:05PM +0530, shashid
Hello,
I need to install postgresql 13.4 on development server , but getting below
errors, please help to resolve this
sudo apt-get install postgresql-13.4
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package postgresql-13.4
E: Coul
rop obsolete function
> DROP FUNCTION pl_profiler_enable(bool);
> https://github.com/bigsql/plprofiler/blob/master/plprofiler--3.5--4.0.sql
>
> Regards,
> Imre
>
> shashidhar Reddy ezt írta (időpont: 2022.
> okt. 29., Szo, 13:40):
>
>>
>> I am getting below error
Any help in this?
On Sat, 29 Oct, 2022, 5:09 pm shashidhar Reddy, <
shashidharreddy...@gmail.com> wrote:
>
> I am getting below error while upgrading postgres from version 12 to 13
> and not sure how to enable the function before upgrading the cluster. Can
> you please help
I am getting below error while upgrading postgres from version 12 to 13 and
not sure how to enable the function before upgrading the cluster. Can you
please help me to resolve this.
error: could not execute query: ERROR: could not find function
"pl_profiler_enable" in file
"/usr/lib/postgresql/1
I am upgrading postures from version 12 to 13 and getting below error when
using pg_upgrade
Error is checking database user is the install user only the install user
can be defined in the new cluster.
Note: I am using postures user
Thank you Pavel it worked for me.
On Sat, 29 Oct, 2022, 12:59 pm Pavel Stehule,
wrote:
>
>
> so 29. 10. 2022 v 9:25 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com> napsal:
>
>> Pavel,
>>
>> After Uninstall plprofiler where can find this to in
I am sorry I have not installed it for version 13 as I am not able to find
the source
On Sat, 29 Oct, 2022, 12:55 pm shashidhar Reddy, <
shashidharreddy...@gmail.com> wrote:
> Pavel,
>
> After Uninstall plprofiler where can find this to install again.
>
> On Sat, 29 Oct,
Pavel,
After Uninstall plprofiler where can find this to install again.
On Sat, 29 Oct, 2022, 12:42 pm Pavel Stehule,
wrote:
> Hi
>
>
> so 29. 10. 2022 v 8:44 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com> napsal:
>
>> Hello,
>>
>> I am
Hello,
I am in a process of upgrading postgresql 12 to version 13, when I am
testing it getting the below error
could not load library $carlib/plprofiler
"/usr/lib/postgresql/13/lib/plprofiler.so":
/usr/lib/postgresql/13/lib/plprofiler.so: undefined symbol: hash_uint32
Could you please l
Thank you Julien! It worked
On Mon, 12 Sep, 2022, 10:19 pm Julien Rouhaud, wrote:
> On Mon, Sep 12, 2022 at 10:14:20PM +0530, shashidhar Reddy wrote:
> > Hello Julien,
> >
> > Can I use this link to install in community edition postgres or is it
> > specific to ente
Hello Julien,
Can I use this link to install in community edition postgres or is it
specific to enterpriseDB
On Mon, 12 Sep, 2022, 7:01 pm Julien Rouhaud, wrote:
> Hi,
>
> On Mon, Sep 12, 2022 at 06:49:21PM +0530, shashidhar Reddy wrote:
> >
> > I am in a process of upgrad
Hello,
I am in a process of upgrading postgres 12 to 13 on ubuntu. When I am
running the test getting error could not load library
"$libdir/plugin_debugger": ERROR: could not load library
"/usr/lib/postgresql/13/lib/plugin_debugger.so":
/usr/lib/postgresql/13/lib/plugin_debugger.so: undefined sym
Thank you all for the inputs, any one tried upgrading from 8.2 to 8.4 and
then used pg_upgrade to upgrade it to any higher version.
On Wed, 6 Jul, 2022, 12:01 am Michael Nolan, wrote:
> I had a client that was stuck on 8.2 for a long time, when they finally
> upgraded to 10, it took several week
Down time 10 to 15 hrs
Hardware specs are also not sure for now as it is client machine.
On Tue, 5 Jul, 2022, 11:22 pm Adrian Klaver,
wrote:
> On 7/5/22 10:48 AM, shashidhar Reddy wrote:
>
> Reply to list also
>
> Ccing list
>
> > Hello Adrian,
> >
> > Os is
Hello,
Could some please let me know how to upgrade postgresql version 8.2 to 13,
as the database size is 20 TB, backup and restore is not possible.
Regards,
Shashidhar
Hello,
Need help on below error after upgrading the postgres from version to 12 to
13.7 I am trying to execute update_extensions.sql script and it throws an
error stating
ERROR: extension "plpgsql_check" has no update path from version "1.2" to
version "1.16". Please help me to fix it.
--
Shash
58 matches
Mail list logo
