Hello
If you have not done it yet, you now have time until Sunday, April 19nd, 2019 to submit your proposals for this year's Swiss PGDay.
Friday, June 28th, 2019
at the University of Applied Sciences (HSR) in Rapperswil (close to Zurich, Switzerland)
The conference milestones:
Call for Spe
I've had a couple of customers complaining of slow searches and doing some
testing last night it seems to be much slower on the live server than on my
test setup.
It's quite a messy query built up by the search code, with lots of joins and
subqueries.
I've downloaded a backup of the customer's l
On 4/5/19 3:43 AM, Rob Northcott wrote:
I’ve had a couple of customers complaining of slow searches and doing some
testing last night it seems to be much slower on the live server than on
my test setup.
It’s quite a messy query built up by the search code, with lots of joins
and subqueries.
Hi Ron,
Thanks for that. I did just run analyse and vacuum on the live database before
I saw your message and it has sorted it out.
Do you think the analyse on its own would have cured it, or would it have been
the vacuum? (vacuum took a long time).
Perhaps I should schedule a vacuum to run per
Rob,
pg_dump/restore gets rid of all the dead space, and you should *always* run
an ANALYZE after pg_restore, since pg_restore doesn't populate the
statistics tables.
On 4/5/19 4:35 AM, Rob Northcott wrote:
Hi Ron,
Thanks for that. I did just run analyse and vacuum on the live database
b
Ah, fair enough – I’ll get into the habit of doing that then. Thanks again.
Rob
From: Ron
Sent: 05 April 2019 11:07
To: pgsql-general@lists.postgresql.org
Subject: Re: Query much slower on 9.6.5 than on 9.3.5
Rob,
pg_dump/restore gets rid of all the dead space, and you should always run an
AN
Hello,
some time ago someone published a website where it was possible to select
two arbitrary Postgres version and then see a list of Bugfixes (and features)
that are missing in the older version of the two.
It was intended to help discussions with admins that are afraid of upgrading.
But I
> "Thomas" == Thomas Kellerer writes:
Thomas> Hello,
Thomas> some time ago someone published a website where it was possible
Thomas> to select two arbitrary Postgres version and then see a list of
Thomas> Bugfixes (and features) that are missing in the older version
Thomas> of the two.
Andrew Gierth schrieb am 05.04.2019 um 13:15:
> Thomas> some time ago someone published a website where it was possible
> Thomas> to select two arbitrary Postgres version and then see a list of
> Thomas> Bugfixes (and features) that are missing in the older version
> Thomas> of the two.
>
> wh
On Tue, Apr 2, 2019 at 11:31 AM Andres Freund wrote:
> Hi,
>
> On 2019-04-02 07:35:02 -0500, Brad Nicholson wrote:
>
> > A blog post would be nice, but it seems to me have something about this
> > clearly in the manual would be best, assuming it's not there already. I
> > took a quick look, and
Hi Sir
EMAIL: maheshpostgr...@gmail.com
MAILSUBJECT: HOST Postgres errors UNIQUE : NUMBER
INCLUDE: ERROR:
INCLUDE: FATAL:
INCLUDE: PANIC:
FILE1: /mnt2/staging/postgres/data/log/LATEST
LASTFILE1: /mnt2/staging/postgres/data/log/postgresql-2019-04-05_00.log
OFFSET1: 10630272
i have configu
Hi,
In 9.6, does such a thing exist? (We just restored a VM from snapshot and I
want to verify the cluster sanity.)
Thanks
--
Angular momentum makes the world go 'round.
There is amcheck:
https://www.postgresql.org/docs/current/amcheck.html
"When the heapallindexed argument to verification functions is true, an
additional phase of verification is performed against the table associated
with the target index relation. This consists of a “dummy” CREATE INDEX
operati
On Fri, Apr 5, 2019 at 7:33 AM Ron wrote:
> In 9.6, does such a thing exist? (We just restored a VM from snapshot and I
> want to verify the cluster sanity.)
amcheck is available for versions 9.4+, though it only appears in
contrib in Postgres 10. There are both yum and deb packages available.
S
Hi!
Is it possible to determine which RLS policies failed on INSERT OR UPDATE?
For instance, this is the error returned when inserting a new record:
**ERROR: new row violates row-level security policy for table "my_table"**
Is it possible to obtain the name of the policy(ies) that denied the
ope
I'm a student at the University of Arizona. My current course is having us
pick a product and do a Security Assessment on it. Part of the assessment
requires us to obtain any authorization necessary before doing the
assessment. Does PostgreSQL require or have any documentation on
authorization to d
Greetings,
* Nicholas Magann (nmag...@email.arizona.edu) wrote:
> I'm a student at the University of Arizona. My current course is having us
> pick a product and do a Security Assessment on it. Part of the assessment
> requires us to obtain any authorization necessary before doing the
> assessment
On 4/5/19 12:10 PM, Nicholas Magann wrote:
I'm a student at the University of Arizona. My current course is having
us pick a product and do a Security Assessment on it. Part of the
assessment requires us to obtain any authorization
necessary before doing the assessment. Does PostgreSQL require
On 4/5/19 2:10 PM, Nicholas Magann wrote:
I'm a student at the University of Arizona. My current course is having us
pick a product and do a Security Assessment on it. Part of the assessment
requires us to obtain any authorization necessary before doing the
assessment. Does PostgreSQL require o
On 2019-04-03 19:42:03 +0400, rihad wrote:
> > And future updates can reuse it, too (an update is very similar to an
> > insert+delete).
>
> Hm, then it's strange our DB takes 6 times as much space compared to freshly
> restored one (only public schema is considered).
This is indeed strange if yo
on 10.2, we're seeing very high cpu usage when doing an update statement
on a relatively small table (1GB). one of the updated columns is text,
about 1k bytes. there are four threads doing similar updates
concurrently to the same table (but different rows). each thread does an
update about ever
On 4/5/19 5:45 PM, Kevin Wilkinson wrote:
on 10.2, we're seeing very high cpu usage when doing an update statement
on a relatively small table (1GB). one of the updated columns is text,
about 1k bytes. there are four threads doing similar updates concurrently
to the same table (but different ro
22 matches
Mail list logo
