Re: CPU is 100% azure rds postgreSQL-11

[Sunil Thakur]

Hi Pavan,

Could you please check the CPU utilization graph and the queries running
during the same timeframe.
I would be able to help more on this issue if I could have more information.

*Thanks and Regards,*
*Sunil M. K. Thakur*
*Database Architect*


On Fri, 8 Jul 2022 at 16:08, Pavan Kumar S  wrote:

> Hi Team,
>
> One of our RDS postgresql -11 version CPU is drastically high
> continuously. we are unable to find what is causing. the server is 4Vcore
> 100 GB storage.  is there any way what is causing the issue.? we have
> datadog integration with custom metrics.
>
> we have done all vacuum and analyze operations, couple of restarts. as
> well.
>
> any Help is appreciated.
>
> thanks
> Pavan
>

Re: Misplaced double quotes in error message

[Sunil Thakur]

It means
Error thrown by Postgres: Hint: Perhaps you meant to reference the column
"t.someColumn".
must be Hint: Perhaps you meant to reference the column t."someColumn".


*Thanks and Regards,Sunil M. K. Thakur*
 *
  *


On Thu, 7 Oct 2021 at 19:09, Adrian Klaver 
wrote:

> On 10/6/21 11:17 PM, Thomas Kellerer wrote:
> > Hello,
> >
> > consider the following table, query and error message:
> >
> >  create table t
> >  (
> >"someColumn" int
> >  );
> >
> >  select t.someColumn
> >  from t;
> >
> >
> >  ERROR: column t.somecolumn does not exist
> >Hint: Perhaps you meant to reference the column "t.someColumn".
> >
> >
> > For someone proficient in SQL it's pretty clear what the error message
> means,
> > but the quotes can be misleading for someone who doesn't really
> understand
> > what's going on.
>
> FYI, errors are generically double quoted:
>
> ERROR:  invalid input syntax for type integer: "one"
>
> This is not specific to identifier quoting.
>
> >
> > I think if the error message quoted the column name the way it should
> actually
> > be used, it would make things easier for someone not used to this, e.g.:
> >
> >Hint: Perhaps you meant to reference the column t."someColumn".
> >
> > Because when the user takes the error message literally they might be
> tempted
> > to use "t.someColumn" just to be confronted with the same error message
> again
> > which then seems even more confusing.
> >
> >
> >
> >
> >
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>
>
>