On Mon, Dec 4, 2017 at 5:52 PM, John R Pierce wrote:
> On 12/4/2017 2:21 PM, chris kim wrote:
>
>>
>>
>> How would I investigate if my database is nearing a transaction wrap
>> around.
>>
>
>
> it would be screaming bloody murder in the log, for one.
>
>
Unfortunately, that comes far too late to
John R Pierce writes:
> On 12/4/2017 2:21 PM, chris kim wrote:
>> How would I investigate if my database is nearing a transaction wrap
>> around.
> it would be screaming bloody murder in the log, for one.
I think the simplest thing is to keep an eye on
select max(age(datfrozenxid)) fro
On Tue, Dec 5, 2017 at 6:12 AM, Alvaro Herrera wrote:
> sql2pg wrote:
>> how about uncommitted(open transactions) . if a segment has 1 committed and
>> 2 uncommitted transactions then will it keep the segment instead deleting it
>> after checkpoint , since it has 2 uncommitted transactions
>
> Th
On 12/4/2017 2:21 PM, chris kim wrote:
How would I investigate if my database is nearing a transaction wrap
around.
it would be screaming bloody murder in the log, for one.
--
john r pierce, recycling bits in santa cruz
Thanks again for helping out.
On Mon, Dec 4, 2017 at 2:12 PM, Andres Freund wrote:
> On 2017-12-04 13:57:52 -0800, David Pacheco wrote:
> > On Mon, Dec 4, 2017 at 12:23 PM, Andres Freund
> wrote:
> > > FWIW, I'd like to see a report of this around the time the issue
> > > occurred before doing
Hello,
How would I investigate if my database is nearing a transaction wrap around.
Best Regards,
Chris
On 2017-12-04 13:57:52 -0800, David Pacheco wrote:
> On Mon, Dec 4, 2017 at 12:23 PM, Andres Freund wrote:
> > FWIW, I'd like to see a report of this around the time the issue
> > occurred before doing anything further here.
> >
>
>
> This failure begins when this process exits, so the best you
On Mon, Dec 4, 2017 at 12:23 PM, Andres Freund wrote:
> Hi,
>
> On 2017-11-20 11:12:08 -0800, David Pacheco wrote:
> > $ ps -opid,rss,vsz,args -p 37627
> > PID RSS VSZ COMMAND
> > 37627 2980 14968 /opt/postgresql/9.2.4/bin/postgres -D /manatee/pg/data
> >
> > I'm not sure what we can infer fr
sql2pg wrote:
> how about uncommitted(open transactions) . if a segment has 1 committed and
> 2 uncommitted transactions then will it keep the segment instead deleting it
> after checkpoint , since it has 2 uncommitted transactions
There is no connection between transaction commit and checkpoint
how about uncommitted(open transactions) . if a segment has 1 committed and
2 uncommitted transactions then will it keep the segment instead deleting it
after checkpoint , since it has 2 uncommitted transactions
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
> On 4 Dec 2017, at 16:57, Nicola Contu wrote:
>
> No I did not run a vacuum analyze. Do you want me to try with that first?
That means your statistics may not be up to date, although by now autovacuum
should have done the job (you didn't turn that off or anything, did you?). Bad
statistics r
Hi,
On 2017-11-20 11:12:08 -0800, David Pacheco wrote:
> $ ps -opid,rss,vsz,args -p 37627
> PID RSS VSZ COMMAND
> 37627 2980 14968 /opt/postgresql/9.2.4/bin/postgres -D /manatee/pg/data
>
> I'm not sure what we can infer from that, as this is a different system,
> and the workload that genera
On Mon, Nov 20, 2017 at 11:12 AM, David Pacheco wrote:
> I understand if the community isn't interested in fixing this case if
> other users aren't seeing it much, but surely it's still a bug that this
> unusual case can result in a deadlock?
>
I've filed bug 14945 to cover this issue:
https://
On Mon, Dec 4, 2017 at 8:50 AM, sql2pg wrote:
> Is Postgres removes the committed transaction after archive. LIke in SQL
> Server , which removes the committed transactions after taking Log backup.
>
If I understand correctly, yes - eventually. The docs explain the behavior
and the configurati
Thank you Tom.
I'll log that suggestion with our internal trouble report for actions to take
on it's next occurrence.
I should have thought of using your suggested view. It's been some time since
I have had any
suspicious postgresql behavior to explore and had forgotten about some of the
bett
On 12/04/2017 04:57 PM, Nicola Contu wrote:
> No I did not run a vacuum analyze. Do you want me to try with that first?
>
> @Tomas:
> Talking abut power management, I changed the profile for tuned-adm
> to latency-performance instead of balanced (that is the default)
>
> that is increasing perfor
"Day, David" writes:
> I'm looking on some insights on the following problem on retrieving table
> column names from the information schema ( postgres 9.6.6 FreeBSD 11.1 )
> When my client starts up up. Each thread ( 10 ) run this command.
> select column_name from information_schema.columns whe
No I did not run a vacuum analyze. Do you want me to try with that first?
@Tomas:
Talking abut power management, I changed the profile for tuned-adm
to latency-performance instead of balanced (that is the default)
that is increasing performances for now and they are similar to centos 6.9.
Time:
Is Postgres removes the committed transaction after archive. LIke in SQL
Server , which removes the committed transactions after taking Log backup.
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
Hi,
I'm looking on some insights on the following problem on retrieving table
column names from the information schema ( postgres 9.6.6 FreeBSD 11.1 )
When my client starts up up. Each thread ( 10 ) run this command.
select column_name from information_schema.columns where table_name =
'pep
On Mon, Dec 4, 2017 at 9:17 AM, Brahmam Eswar wrote:
> Hi ,
>
> Is there anyway to pull the complete information of tables in a particular
> schema .
>
> Table_Name ,Num_Rows,Columns,Indexed_Columns,Triggers.
>
>
>
> The context of this request is ,we are migrating the database from Oracle
> to P
Did you run ANALYZE on your tables before the test?
On 4 December 2017 at 16:01, Tomas Vondra wrote:
>
> On 12/04/2017 02:19 PM, Nicola Contu wrote:
> ...>
>> centos 7 :
>>
>> dbname=# \timing Timing is on. cmdv3=# SELECT id FROM
>> client_billing_account WHERE name = 'name'; id --- * (1
On 12/04/2017 02:19 PM, Nicola Contu wrote:
...>
> centos 7 :
>
> dbname=# \timing Timing is on. cmdv3=# SELECT id FROM
> client_billing_account WHERE name = 'name'; id --- * (1 row)
> Time: 3.884 ms
>
> centos 6.9
>
> dbname=# SELECT id FROM client_billing_account WHERE name = 'name';
Bharanee Rathna writes:
> To be more specific, I expected the output of both these queries to be the
> same.
> # select '2017-12-01 11:00:00 +11:00'::timestamp with time zone at time
> zone '+11:00';
> # select '2017-12-01 11:00:00 +11:00'::timestamp with time zone at time
> zone 'Australia/Melbou
To make a better testing, I used a third server.
This is identical to the centos 7 machine, and it is not included in the
replica cluster.
Nobody is accessing this machine, this is top :
top - 14:48:36 up 73 days, 17:39, 3 users, load average: 0.00, 0.01, 0.05
Tasks: 686 total, 1 running, 685
These are the timings in centos 7 :
Time: 4.248 ms
Time: 2.983 ms
Time: 3.027 ms
Time: 3.298 ms
Time: 4.420 ms
Time: 2.599 ms
Time: 2.555 ms
Time: 3.008 ms
Time: 6.220 ms
Time: 4.275 ms
Time: 2.841 ms
Time: 3.699 ms
Time: 3.387 ms
These are the timings in centos 6:
Time: 1.722 ms
Time: 1.670 ms
centos 7 :
Time: 3.884 ms
centos 6.9
Time: 1.620 ms
Is there anything you can advice to solve or identify the problem?
Can you run this query 10 times on each server and note the timings?
I'd like to see the reproducability of this.
Also: both machines are otherwise idle (check with top o
Hi ,
Is there anyway to pull the complete information of tables in a particular
schema .
Table_Name ,Num_Rows,Columns,Indexed_Columns,Triggers.
The context of this request is ,we are migrating the database from Oracle
to PostgreSQl,,so we need to verify the data after perform data migration
fr
On Mon, Dec 4, 2017 at 6:57 AM, Job wrote:
> Hi guys,
>
> thank you for everything.
>
> Thanks for the queries, i ntocied the lock comes from here:
> 16389 | flashstart |17409 | public | confs
> | 5646 | postgres | tuple| ExclusiveLock| t
>|
Hi all,
I'd like to resurrect this thread, as it seems that there was no definitive
answer:
https://www.postgresql.org/message-id/959f28ef-4245-8349-eff9-0ff5f666df03%40lucee.org
Does anyone know how to add an IDENTITY column to an existing non-empty
table? Like Igal, I get the error message "col
Hello,
we recently upgrade OS from centos 6.9 to a new server with centos 7.
The centos 6.9 server has became the preproduction server now.
We are running postgres 9.6.6 on both servers.
They are both on SSD disk, these are the only differences :
- DB partition on centos 7 is on a RAID 10
- fil
OK, have installed perf and will report back when the problem gets noticeable.
Martin.
On 04/12/2017, 12:40, "Michael Paquier" wrote:
On Mon, Dec 4, 2017 at 9:03 PM, Martin Moore
wrote:
> After a few days, it’s noticeable that the Postgres on the publisher node
is constantly using a
On Mon, Dec 4, 2017 at 9:03 PM, Martin Moore wrote:
> After a few days, it’s noticeable that the Postgres on the publisher node is
> constantly using a lot of cpu (26% today) and having a big impact on the
> system performance even when doing very little. Logging on to the subscriber
> and remo
I see that the segfault is under active discussion but just wanted to ask
if increasing the max_connections to mitigate the DSM slots shortage is the
way to go?
--
regards,
Jakub Glapa
On Mon, Nov 27, 2017 at 11:48 PM, Thomas Munro <
thomas.mu...@enterprisedb.com> wrote:
> On Tue, Nov 28, 2017
On Mon, 2017-12-04 at 14:03 +1100, Bharanee Rathna wrote:
> To be more specific, I expected the output of both these queries to
> be the same.
>
> # select '2017-12-01 11:00:00 +11:00'::timestamp with time zone at
> time zone '+11:00';
> timezone
> -
> 2017-11-3
I’ve got two Postgres 10/Debian stretch systems and have added a
publish/subscribe on a single table that isn’t updated very often. The
subscriber node is doing very little else.
After a few days, it’s noticeable that the Postgres on the publisher node is
constantly using a lot of cpu (26% toda
Hi guys,
thank you for everything.
Thanks for the queries, i ntocied the lock comes from here:
16389 | flashstart |17409 | public | confs
| 5646 | postgres | tuple| ExclusiveLock| t | 2
16389 | flashstart |17409 | public
37 matches
Mail list logo
