[GENERAL] Missing folder rhel-6Workstation-x86_64 for 9.6 repo (redhat)

Hi, it looks like that the folder 'rhel-6Workstation-x86_64' does not exist any more for 9.6 (redhat). Is this intentional or has this folder just been forgotten? Is it possible that someone can create this? Thank you in advance. Sari -- Sari Thiele University of Oslo

[GENERAL] Re: [HACKERS] Why restore_command is called for existing files in pg_xlog?

Hi Jeff, On Mon, Jun 12, 2017, at 06:42 PM, Jeff Janes wrote: > On Mon, Jun 12, 2017 at 5:25 AM, Alex Kliukin > wrote:>> __ >> >> On Fri, Jun 2, 2017, at 11:51 AM, Alexander Kukushkin wrote: >>> Hello hackers, >>> There is one strange and awful thing I don't understand about

Re: [GENERAL] ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

Harry Ambrose writes: > Not sure whether its relevant or not, however upon adding an ANALYSE before > the second vacuum the issue has not presented when testing. I have managed > 95 cycles thus far. I'm still unable to reproduce :-( --- I ran about two dozen cycles

Re: [GENERAL] ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

Hi, Not sure whether its relevant or not, however upon adding an ANALYSE before the second vacuum the issue has not presented when testing. I have managed 95 cycles thus far. BEGIN; CREATE TABLE x (id BIGSERIAL PRIMARY KEY, payload1 VARCHAR, payload2 VARCHAR, payload3 VARCHAR, payload4 BIGINT,

Re: [GENERAL] pg_upgrade --link on Windows

On Fri, Jun 9, 2017 at 07:55:55AM -0700, Adrian Klaver wrote: > On 06/09/2017 07:39 AM, Arnaud L. wrote: > >See this page for more details : > >http://cects.com/overview-to-understanding-hard-links-junction-points-and-symbolic-links-in-windows/ > > > > > >Under "Hard Link (Linking for individual

Re: [GENERAL] pg_catalog tables don't have constraints?

Thomas Kellerer wrote: > kbran...@pwhome.com schrieb am 09.06.2017 um 20:57: > > Neil Anderson wrote: > > > >> I've been exploring the pg_catalog tables and pointed a couple of > >> tools at it to extract an ER diagram for a blog post. At first I > >> thought it was a

[GENERAL] autovacuum holds exclusive lock on table preventing it from to be updated

Hi, I run postgresql 9.3.17. I am preparing for a major database schema upgrade. I copied production database to test system using pg_basebackup. Having started the database and waited for all WALs to be applied I proceeded to run schema modifications. Immediately I run into issue -

Re: [GENERAL] FULL_PAGE_WRITES

what's the table and index look like? how do you test? Is it HOT update? For update table and index ,you can read this: http://www.dbrnd.com/2016/12/postgresql-increase-the-speed-of-update-query-using-hot-update-heap-only-tuple-mvcc-fill-factor-vacuum-fragmentation/ 2017年6月13日 1:06

Re: [GENERAL] autovacuum holds exclusive lock on table preventing it from to be updated

Am 13. Juni 2017 20:04:04 MESZ schrieb Dmitry O Litvintsev : > >I >wraparound)| 2017- >| t | enstore | autovacuum: VACUUM public.t_inodes (to prevent >wraparound)| 2017-06-13 12:31:04.870064-05 | >00:28:50.276437 | 40672 >chimera |