Re: [GENERAL] Corrupt index

On Tue, Aug 15, 2017 at 12:24 PM, Daryl Stultz >>You've given no details at all. What business pattern? What does the >>index and table look like? Hi Peter. There are no details that are obvious to me that I should be providing. The business process is one of a thousand that the application

Re: [GENERAL] Corrupt index

On 15 August 2017 21:24:29 GMT+02:00, Daryl Stultz wrote: >Hello, > >We are using PostgreSQL 9.3.14 on a managed Amazon RDS with a > Are you using reindex concurrently? There was a bugfix in 9.3.16 (+-1, i'm not sure). Regards, Andreas -- 2ndQuadrant - The

Re: [GENERAL] Corrupt index

On 15 August 2017 21:54:56 GMT+02:00, Daryl Stultz wrote: > >>>We are using PostgreSQL 9.3.14 on a managed Amazon RDS with a > > >>Are you using reindex concurrently? There was a bugfix in 9.3.16 (+-1, >i'm not sure). > >Hi Andreas, not that I'm aware of. I issue

Re: [GENERAL] Corrupt index

>>We are using PostgreSQL 9.3.14 on a managed Amazon RDS with a >Are you using reindex concurrently? There was a bugfix in 9.3.16 (+-1, i'm not >sure). Hi Andreas, not that I'm aware of. I issue "reindex table mytable" to get out of the bad situation. I'm not sure if you are saying this bug

Re: [GENERAL] Corrupt index

On Tue, Aug 15, 2017 at 12:24 PM, Daryl Stultz wrote: > We have a recurring problem that we can get out of with "reindex table > mytable". Basically we can't find a particular record or two using the > primary key and after reindexing we can. There does seem to be a

Re: [GENERAL] Corrupt index

On 8/15/2017 1:07 PM, Andreas Kretschmer wrote: I only wanted to exclude it. Anyway, you should install the latest patches. he can't, with RDS, he's at the mercy of Amazon for all sysadmin duties. -- john r pierce, recycling bits in santa cruz -- Sent via pgsql-general mailing list

[GENERAL] How to delete default privileges

I have a DB where we changed ownership of all objects. We had: ALTER DEFAULT PRIVILEGES FOR ROLE old_dbowner GRANT SELECT ON tables TO dbgroup_ro_group; ALTER DEFAULT PRIVILEGES FOR ROLE old_dbowner GRANT SELECT ON sequences TO dbgroup_ro_group; ALTER DEFAULT PRIVILEGES FOR ROLE

Re: [GENERAL] How to delete default privileges

On Tue, Aug 15, 2017 at 3:02 PM, Francisco Reyes wrote: > I have a DB where we changed ownership of all objects. > > We had: > > ALTER DEFAULT PRIVILEGES FOR ROLE old_dbowner GRANT SELECT ON tablesTO > dbgroup_ro_group; > ALTER DEFAULT PRIVILEGES FOR ROLE old_dbowner GRANT

[GENERAL] Corrupt index

Hello, We are using PostgreSQL 9.3.14 on a managed Amazon RDS with a Multi-zone failover configuration. We do not have access to the hardware or file system. Fsync is enabled. We have a recurring problem that we can get out of with "reindex table mytable". Basically we can't find a particular

Re: [GENERAL] Corrupt index

On 8/15/2017 1:07 PM, Andreas Kretschmer wrote: >> I only wanted to exclude it. Anyway, you should install the latest patches. >he can't, with RDS, he's at the mercy of Amazon for all sysadmin duties. For many things, yes. I do have options to upgrade PG. We could probably do a minor upgrade

[GENERAL] Begginers question

Hi So I have been playing with an streaming cluster. I have the replication working I believe. But whilst attempting to do an import of my original DB, I filled up my disk pg_xlog directory. Strangley I have tried this before and not filled this up. so 1) why did it fill up this time and not

Re: [GENERAL] WAL replication wrong collate

On Tue, Aug 15, 2017 at 4:45 AM, basti wrote: > i have fixed. pg_update has create a wrong cluster Let's be sure that we are not talking about a bug here, because you are giving no details so it is hard to know if what you are seeing is caused by an incorrect operation,

Re: [GENERAL] cluster question

On 15 August 2017 at 16:35, Andreas Kretschmer wrote: > > > Am 15.08.2017 um 05:15 schrieb Alex Samad: > >> Hi >> >> Quick question. I have a 2 node cluster - each node has its own ip. >> >> But from reading this, I really need a 3rd ip, which potentially floats >>

Re: [GENERAL] WAL replication wrong collate

i have fixed. pg_update has create a wrong cluster On 14.08.2017 20:52, basti wrote: Hello, i try to replicate my database. what i have done? - create a cluster on slave (UTF8, en_US.utf8 collate/c_type) - stop cluster and cleanup datadir - do basebackup from master - start db-cluster

Re: [GENERAL] cluster question

Am 15.08.2017 um 05:15 schrieb Alex Samad: Hi Quick question. I have a 2 node cluster - each node has its own ip. But from reading this, I really need a 3rd ip, which potentially floats between the nodes to which ever is the master / rw node. Is that right? Sort of makes sense I guess