Hello,
As our env os version is different, some is centos 7.4, some is 7.5 and 7.6
..., and there is only one company repo, as I compare the packages size and
date, seems same, If we can just use 7.6 packages please?
https://download.postgresql.org/pub/repos/yum/13/redhat/rhel-7.4-x86_64/
https:/
On 6/29/21 2:30 PM, Ray O'Donnell wrote:
On 29/06/2021 22:10, Adrian Klaver wrote:
The queued bookings are for a particular aircraft or a particular time
slot?
They're for an aircraft. On the old system, they could only be for a
slot - so if someone had booked, say, a two-hour slot, then an
On 29/06/2021 22:10, Adrian Klaver wrote:
The queued bookings are for a particular aircraft or a particular time
slot?
They're for an aircraft. On the old system, they could only be for a
slot - so if someone had booked, say, a two-hour slot, then anyone
queued behind them could only queue
On 6/29/21 12:49 PM, Ray O'Donnell wrote:
On 29/06/2021 20:43, Adrian Klaver wrote:
An ounce of prevention is worth a pound of cure:
1) Install btree_gist
create extension btree_gist ;
2) create table bookings (
booking_id bigint not null,
aircraft_id integer,
booking_time_star
George Tarasov writes:
> So, my questions are there any rules / descriptions / agreements inside
> the PostgreSQL Project that define which global variables inside a core
> code should by specified by a PGDLLIMPORT and which should not?? Or
> there is freedom; you need this variable in the exte
Dear all!
(comment: my question relates only to the development area; so, please,
re-post to pgsql-hackers if it is allowed).
I use PostgreSQL under Windows quiet often and make my own builds in
msys2/mingw64 environment. Also I often experiments with the different
third-party extensions fro
On 29/06/2021 20:43, Adrian Klaver wrote:
An ounce of prevention is worth a pound of cure:
1) Install btree_gist
create extension btree_gist ;
2) create table bookings (
booking_id bigint not null,
aircraft_id integer,
booking_time_start timestamptz,
booking_time_end timest
On 6/28/21 3:05 AM, Ray O'Donnell wrote:
On 28/06/2021 00:52, Adrian Klaver wrote:
On 6/27/21 3:41 PM, Ray O'Donnell wrote:
Here's a slightly simplified example:
create table bookings (
booking_id bigint not null,
booking_time tstzrange not null,
constraint bookings_pk prima
> On Jun 29, 2021, at 11:02 AM, Ron wrote:
>
> What's an IOS?
An Index Only Scan. See
https://www.postgresql.org/docs/14/indexes-index-only-scans.html
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On 6/29/21 12:46 PM, Tom Lane wrote:
Ron writes:
On 6/29/21 11:42 AM, Tom Lane wrote:
If there's a significant difference in relallvisible fractions, that
would point to something different in your VACUUM housekeeping on
the two systems.
Prod is brand new. Loaded on Saturday; we saw this pro
> On Jun 29, 2021, at 10:33 AM, Ron wrote:
>
> Prod is brand new. Loaded on Saturday; we saw this problem on Sunday during
> pre-acceptance. Thus, while running ANALYZE was top of the list of Things To
> Do, running VACUUM was low.
>
> Is that a mistaken belief?
You might want to run VAC
Ron writes:
> On 6/29/21 11:42 AM, Tom Lane wrote:
>> If there's a significant difference in relallvisible fractions, that
>> would point to something different in your VACUUM housekeeping on
>> the two systems.
> Prod is brand new. Loaded on Saturday; we saw this problem on Sunday during
> pre
On 6/29/21 11:42 AM, Tom Lane wrote:
Ron writes:
On 6/29/21 10:41 AM, Michael Lewis wrote:
What's an example query that uses indexes on test and does not on live?
SELECT COUNT(*) FROM sep_info_report_extract;
On prod, there's a list of "Parallel Seq Scan on _partname" records in
the EXPLA
Ron writes:
> On 6/29/21 10:41 AM, Michael Lewis wrote:
>> What's an example query that uses indexes on test and does not on live?
> SELECT COUNT(*) FROM sep_info_report_extract;
> On prod, there's a list of "Parallel Seq Scan on _partname" records in
> the EXPLAIN output, while the test sy
Other than rows being frozen on test (and not on live), I'm not aware of
anything that would push the planner to choose to do an index scan on an
entire table. Maybe someone else will chime in. Or, if you try running
vacuum freeze on live and can verify if that changes the result.
I'm not sure why
On 6/29/21 10:41 AM, Michael Lewis wrote:
Are vacuum and analyze happening regularly on the live system?
Yes. There's a nightly cron job which vacuums those it thinks needs it
(though it's INSERT-heavy), and ditto ANALYZE.
Specifically, I ran ANALYZE on the prod table just before running th
Are vacuum and analyze happening regularly on the live system? What's an
example query that uses indexes on test and does not on live? Does the live
system show poor estimates when executing 'explain analyze select...' and
the test system show semi-accurate row estimates?
50 million seems to be a
Postgresql 12.5
I've got a big (about 50M rows, but 1.4TB because of xml attachments)
partitioned table full of data that we're seeing sequential scans on, even
though there are supporting indices. Will adding CHECK constraints on the
children, which match the partition ranges influence the qu
18 matches
Mail list logo
