HI Everyone,
Below DB query is showing below error on postgresql9.3.
SELECT '\'' || t2.name || '\'', '\'' || t1.phone_number || '\'', '\'' ||
t1.details || '\'', '\'' || t1.description || '\'', '\'' || (CASE WHEN t1.s_id
IS NULL THEN 'N/A' ELSE t3.s_type END) || '\'', '\'' || t1.s_id || '\'' FRO
Dear All,
Thanks for your support.
Could you please assist for changelog version option used to find the
differences between the versions.
In addition we required information of changes done in all releases from 8.1.2
to 9.3.6.
Thanks in advance .
Regards,
Yogesh
s://www.postgresql.org/docs/9.3/static/release.html
>
> you can find all release notes, including changelogs for all versions.
Also a one page version:
https://bucardo.org/postgres_all_versions.html
>
> HTH,
> Moreno.
>
> Il 10/06/2016 13:17, Yogesh Sharma ha scritto:
>
, 2016 7:18 PM
To: Albe Laurenz
Cc: Yogesh Sharma; Adrian Klaver; Moreno Andreo; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Changelog version from 8.1.2 to 9.3.6
On Wed, Jun 15, 2016 at 3:31 AM, Albe Laurenz
mailto:laurenz.a...@wien.gv.at>> wrote:
Yogesh Sharma wrote:
> I have doubt
Dear Team,
Thanks for your support and suggestion.
We are using below postgresql rpm.
postgresql-8.1.18-2.1
In our system, below error is found and occurring is very frequent.
CONTEXT: writing block 53 of relation 1663/16385/280951
ERROR: could not open relation 1663/16385/280951: No such file
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Request to share information regarding postgresql
pg_xlog file.
On 9/14/2016 10:09 PM, Yogesh Sharma wrote:
Thanks for your support and suggestion.
We are using below postgresql rpm.
postgresql-8.1.18-2.1
thats not the full RPM name, thats just the
pg_xlog file.
On 9/15/2016 12:25 AM, Yogesh Sharma wrote:
Dear John,
Thanks for your support.
Please find below name of rpm.
RPMS/postgresql-8.1.18-2.1.x86_64.rpm
RPMS/postgresql-devel-8.1.18-2.1.x86_64.rpm
RPMS/postgresql-libs-8.1.18-2.1.x86_64.rpm
RPMS/postgresql-python-8.1.18-2.1.x86_64.rpm
Dear All,
Thanks for your support.
I need to take source rpm for below version for rhel.
postgresql-8.1.18-2.1
Could you please share link, so that I will take.
I have tried to search but could not found.
Regards,
Yogesh
Dear All,
Thanks in advance.
In my Linux system, below error is found and after 10~12 hours, WAL file in
pg_xlog directory are increased continuously.
PostgreSQL:ERROR: deadlock detected
DETAIL: Process 12345 waits for AccessShareLock on relation 16446 of database
16385; blocked by process 23
ral-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Monday, November 14, 2016 4:19 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Request to share information regarding deadlock in
postgresql-8.1.18
On 11/13/2016 11:01 PM, Yogesh Sharma w
Dear All,
Thanks for your support.
I am using postgresql 9.3.6 rpm in RHEL6 version.
In postgresql logs, I have found below error messages.
ERROR: null value in column "column name" violates not-null constraint.
Second error found:
ERROR: there is no unique constraint matching given keys for
e_id.
At this time, DB is shutdown.
This shutdown is related to this error or not?
Regards,
Yogesh
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Charles Clavadetscher
Sent: Wednesday, November 16, 2016 3:44 PM
To: Yo
Dear All,
Thanks for your support.
Could you please share your opinion for deadlock resolution.
Process 5764 waits for AccessShareLock on relation 16459 of database 16385;
blocked by process 4970.
Process 4970 waits for ShareLock on relation 16502 of database 16385; blocked
by process 5764.
@postgresql.org] On Behalf Of John R Pierce
Sent: Thursday, November 17, 2016 12:04 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Request to share information regarding deadlock in
postgresql-9.3.6
On 11/16/2016 6:22 PM, Yogesh Sharma wrote:
> process 5764 is waiting for relat
Dear All,
Thanks in advance.
I found below deadlock in postgresql logs.
I cannot change calling of REINDEX and insert query sequence because it is
execute automatically through some cron script.
ERROR: deadlock detected
DETAIL: Process 2234 waits for AccessShareLock on relation 16459 of datab
/24/2016 5:44 PM, Yogesh Sharma wrote:
> I cannot change calling of REINDEX and insert query sequence because it is
> execute automatically through some cron script.
any cron scripts are your own doing, so this statement makes no sense at all.
--
john r pierce, recycling bits in sant
Dear All,
Thanks for your support.
I am using postgresql 9.3.6 on RHEL6.6 machine.
In my production environment, Some script are executing automatically
through cron.
These script are performing insert and update operation.
Also, every hour,i am performing VACUUM and REINDEX operation on table.
Adding subject line
Dear All,
Thanks for your support.
I am using postgresql 9.3.6 on RHEL6.6 machine.
In my production environment, Some script are executing automatically
through cron.
These script are performing insert and update operation.
Also, every hour,i am performing VACUUM and REI
:
> On 21 December 2016 at 09:59, Yogesh Sharma > wrote:
> > Also, every hour,i am performing VACUUM and REINDEX operation on table.
>
> Why are you running REINDEX every hour? That's a very unusual thing to
> do, you'd need a pretty good reason for that.
>
> --
in your inserts and updates
> operations why don't you try drop index and CREATE INDEX CONCURRENTLY.
> As Alban said you I don't recommend you to execute reindex every hour, at
> least try to reduce the scope of the reindex to the minimal object.
>
>
>
>
>
>
Dear Vick,
I have responded on previously mail.
In my production system, there are lot of read write operation performed
every hour.
Regards,
yogesh
On Wednesday, December 21, 2016, Vick Khera wrote:
> On Wed, Dec 21, 2016 at 4:02 AM, Yogesh Sharma > wrote:
> > Also, eve
Dear Steven,
Thanks for your reply.
Yes. You are correct.
Regards,
Yogesh
On Wednesday, December 21, 2016, Steven Winfield <
steven.winfi...@cantabcapital.com> wrote:
> > In my production system, there are lot of read write operation
> performed every hour.
>
>
>
> Apologies if this sounds patr
Dear All,
Thanks for your support.
Could you please tell me, how to recover my system.
I am facing below errors.
---
could not open relation 1663/16385/1299988: No such file or directory
---
This message is continuous occurred in system .
I have
2016 1:45 PM
To: Yogesh Sharma; pgsql-general
Subject: Re: [GENERAL] Issue during postgresql startup
On Thu, 28 Apr 2016 15:22 Yogesh Sharma,
mailto:yogesh1.sha...@nectechnologies.in>>
wrote:
Dear All,
Thanks for your support.
Could you please tell me, how to recover my system.
I a
postgresql startup
On 4/28/2016 12:21 AM, Yogesh Sharma wrote:
Could you please tell me, how to recover my system.
I am facing below errors.
---
could not open relation 1663/16385/1299988: No such file or directory
---
This message is continuou
ral@postgresql.org
Subject: Re: [GENERAL] Issue during postgresql startup
On 4/28/2016 1:33 AM, Yogesh Sharma wrote:
>did you get that 'no such file or directory' error before or after you reset
>the transaction logs ?
The error message is coming before.
that means your fil
tically.
I’ll appreciate any kind of opinion on my understanding.
Thanks,
Yogesh Sharma
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Thursday, April 28, 2016 2:51 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENER
Dear All,
Could you please update your suggestion on below mail
Regards,
Yogesh
From: Yogesh Sharma
Sent: Friday, April 29, 2016 3:57 PM
To: John R Pierce; pgsql-general@postgresql.org
Subject: RE: [GENERAL] Issue during postgresql startup
Dear All,
I am sharing my further observation
Dear All,
I want to upgrade RHEL 5.4 to RHEL 6.5.
So, could you please let me know, which postgresql version is stable for RHEL
6.5?
Regards,
Yogesh
DISCLAIMER:
---
The contents
Dear All,
Compatibility issues of 9.3 are more.
So, please guide which version is suitable.
Regards,
Yogesh
-Original Message-
From: Devrim Gündüz [mailto:dev...@gunduz.org]
Sent: Thursday, August 28, 2014 7:34 PM
To: Yogesh. Sharma
Cc: pgsql-general@postgresql.org
Subject: Re
age-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of David G Johnston
Sent: Friday, August 29, 2014 9:22 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Help related to Postgresql for RHEL 6.5
Yogesh. Sharma wrote
> Compatibility issu
Dear All,
I am facing some issue during postgresql service stop.
Issue:-
[root@localhost postgresql-9.0.18]# runuser -l postgres -c
'/usr/pgsql/bin/pg_ctl stop -D '\''/var/lib/pgsql/data'\'' -s -m fast'
/usr/pgsql/bin/pg_ctl: error while loading shared libraries: libpq.so.5: cannot
open shared o
Dear all,
Thanks for your support.
I need to perfrom INSERT and REINDEX operation exclusively.
For example:
If REINDEX operation is in progress then INSERT operation will wait and
vice versa.
Please let me know if any approach is available.
Regards,
Yogesh sharma
Dear David,
I want to apply explicitly lock mechanism once inset operation is in
progress then REINDEX will wait.
And vice versa.
So, please let me know this type of handling is possible.
Regrds,
Yogesh
On Wednesday, March 8, 2017, David G. Johnston
wrote:
> On Tuesday, March 7, 2017, Yog
Dear Scott,
How to handle table with token?
How to implement this?
Regards,
Yogesh
On Wednesday, March 8, 2017, Scott Marlowe wrote:
> On Tue, Mar 7, 2017 at 11:55 PM, Scott Marlowe > wrote:
> > On Tue, Mar 7, 2017 at 11:21 PM, Yogesh Sharma > wrote:
> >> Dear Dav
Dear Albe,
Thanks for your support.
I observed there is some problem in REINDEX operation in older PostgreSQL
versions.
That why i want to add explicitly lock.
Regards,
Yogesh
On Wednesday, March 8, 2017, Albe Laurenz wrote:
> Yogesh Sharma wrote:
> > I want to apply explic
>
> Dear All,
We have one perl script that is opening DB connection and performaing
insert DB operation.When duplicate entry Comming in query,Postgres
forecfully killing process itself and in Postgres log "unexpected EOF on
client connection" error is Comming.
This issue is not Comming every time
is killed.
On Tuesday, September 12, 2017, Daniel Verite
wrote:
> Yogesh Sharma wrote:
>
> > We have found child script is killed by signal 13 SIGPIPE. When duplicate
> > key violates error occured, script is killed but not all time.
>
> "child script" a
Dear All,
Thanks in advance.
We are using Postgres 8.1.18 version.
In Postgres log, we found below logs.
–-
CONTEXT:writing block 0 of relation 1664/0/1260
ERROR: could not write block 0 of relation 1664/0/1260: Bad address
Due to this pglog_Xlog dire
Dear all,
As current situation, i can not upgrade on higher version.
Is there any recovery command available?
Regards,
Yogesh
On Thursday, September 14, 2017, Gavin Flower
wrote:
> On 14/09/17 15:29, Yogesh Sharma wrote:
>
>> Dear All,
>>
>> Thanks in advance.
>
>>What you could do is copying its contents to a large disk, and then allow
it to recover from the crash.
I will copy the PGDATA into large disk. After that it is require to
execute some specific command or automatically recovery will start?
If any command is require to execute please let me know.
Hello,
We are using postgres for one of our application. Currently using
Postgres 8.3 with CentOS 5.3 x86_64
We are using inherited tables. Base table has 3 columns:
entry_date timestamp with time zone
nametext
valuetext
pk is timestamp
data tables are derived from this base table wit
42 matches
Mail list logo
