Re: Restore from dumps

2018-07-26 Thread Nicola Contu
That worked. Thanks guys. 2018-07-25 16:33 GMT+02:00 Nicola Contu : > yeah, we updated that function in production to says public.all_days. > I will let you know at the next restore. > > Thanks guys, appreciated. > > 2018-07-25 16:28 GMT+02:00 Tom Lane : > >> Laurenz Albe writes: >> > Nicola Con

Re: Permission denied on schema for all users on insert to table with fk

2018-07-26 Thread Adrian Klaver
On 07/26/2018 03:52 AM, Leland Weathers wrote: And a more complete example of what we are seeing with multiple accounts. This particular set is from an account that has their role set to that of the database & schema owner which is different than the table owner role.

Re: Permission denied on schema for all users on insert to table with fk

2018-07-26 Thread Adrian Klaver
On 07/26/2018 06:57 AM, Leland Weathers wrote: Before you mentioned a trigger. I am not seeing that in the schema you sent. Is there one and if so what is it's definition and that of its associated function? I was referring to the "built-in" PostgreSQL system trigger for validat

Re: Permission denied on schema for all users on insert to table with fk

2018-07-26 Thread Leland Weathers
On Wed, Jul 25, 2018 at 11:32 AM, Adrian Klaver wrote: > On 07/25/2018 06:40 AM, Leland Weathers wrote: > >> I just ran into an issue on 9.5.13 after creating a new schema with a set >> of tables in them, that no accounts (including schema / table owners) can >> insert into a table with a fk rela

Re: Permission denied on schema for all users on insert to table with fk

2018-07-26 Thread Leland Weathers
On Thu, Jul 26, 2018 at 8:31 AM, Adrian Klaver wrote: > On 07/26/2018 03:52 AM, Leland Weathers wrote: > >> >> >> > > > >> And a more complete example of what we are seeing with multiple >> accounts. This particular set is from an account that has their role >> set to that of the data

Re: Permission denied on schema for all users on insert to table with fk

2018-07-26 Thread Leland Weathers
On Thu, Jul 26, 2018 at 9:19 AM, Adrian Klaver wrote: > On 07/26/2018 06:57 AM, Leland Weathers wrote: > > >> >> Before you mentioned a trigger. I am not seeing that in the schema >> you sent. Is there one and if so what is it's definition and that of >> its associated function? >> >>

Re: logical replication snapshots

2018-07-26 Thread Dimitri Maziuk
On 07/25/2018 07:57 PM, Andres Freund wrote: > On 2018-07-25 12:31:01 -0700, Adrian Klaver wrote: >>> Would "permission denied" be relevant? >> >> Logical decoding is something I am still learning. The "permission denied" >> would to me be relevant only to the extent that it seems to be provoking:

Re: logical replication snapshots

2018-07-26 Thread Adrian Klaver
On 07/26/2018 10:54 AM, Dimitri Maziuk wrote: On 07/25/2018 07:57 PM, Andres Freund wrote: On 2018-07-25 12:31:01 -0700, Adrian Klaver wrote: Would "permission denied" be relevant? Logical decoding is something I am still learning. The "permission denied" would to me be relevant only to the

Re: logical replication snapshots

2018-07-26 Thread Andres Freund
On 2018-07-26 12:54:19 -0500, Dimitri Maziuk wrote: > >> "LOG: logical decoding found consistent point at 19/E6942440" > >> DETAIL: There are no running transactions." > >> > >> Others with more experience in this area would need to fill whether that > >> might account for the 13 million files in

Re: logical replication snapshots

2018-07-26 Thread Dimitri Maziuk
On 07/26/2018 02:54 PM, Adrian Klaver wrote: > On 07/26/2018 10:54 AM, Dimitri Maziuk wrote: >> I'm not sure what happened, I remember the initial sync of that >> particular schema failing on one table only, but looking at it now, all >> tables are empty on the subscriber. > > To me that indicate

Re: logical replication snapshots

2018-07-26 Thread Adrian Klaver
On 07/26/2018 02:06 PM, Dimitri Maziuk wrote: On 07/26/2018 02:54 PM, Adrian Klaver wrote: On 07/26/2018 10:54 AM, Dimitri Maziuk wrote: I'm not sure what happened, I remember the initial sync of that particular schema failing on one table only, but looking at it now, all tables are empty on

Re: logical replication snapshots

2018-07-26 Thread Dimitri Maziuk
On 07/26/2018 04:39 PM, Adrian Klaver wrote: > The thing that has me somewhat confused is: > > ERROR: permission denied for schema macromolecules > > I would thought the replication user could access that. The more I look at the errors, the less sense it all makes. Let me ask a different quest

Re: logical replication snapshots

2018-07-26 Thread Adrian Klaver
On 07/26/2018 03:01 PM, Dimitri Maziuk wrote: On 07/26/2018 04:39 PM, Adrian Klaver wrote: The thing that has me somewhat confused is: ERROR: permission denied for schema macromolecules I would thought the replication user could access that. The more I look at the errors, the less sense it

Re: logical replication snapshots

2018-07-26 Thread Dimitri Maziuk
On 07/26/2018 05:34 PM, Adrian Klaver wrote: > On 07/26/2018 03:01 PM, Dimitri Maziuk wrote: >> Let me ask a different question: if I drop and re-create a published >> table on the publisher without doing anything to the publication and >> subscription, what happens? > > Take a look at: > > http

Re: logical replication snapshots

2018-07-26 Thread Adrian Klaver
On 07/26/2018 04:48 PM, Dimitri Maziuk wrote: On 07/26/2018 05:34 PM, Adrian Klaver wrote: On 07/26/2018 03:01 PM, Dimitri Maziuk wrote: Let me ask a different question: if I drop and re-create a published table on the publisher without doing anything to the publication and subscription, what