>
> We run a master server and a hot standby server. Reporting users login to
> the standby server to run long queries. However, their login is also valid
> on the master server. Is it possible to prevent a user from logging in to
> the master server?
>
What I do is use roles as groups, and
I'm assuming based on the "SSL error" that you have ssl set to 'on'. What's
your ssl_renegotiation_limit? The default is 512MB, but setting it to 0 has
solved problems for a number of people on this list, including myself.
Sherrylyn
On Thu, Sep 24, 2015 at 3:57 PM, Francisco Reyes
Ah, yes, it's been removed from 9.5:
http://www.postgresql.org/docs/9.5/static/release-9-5.html
Good to know.
On Thu, Sep 24, 2015 at 4:34 PM, Alvaro Herrera <alvhe...@2ndquadrant.com>
wrote:
> Sherrylyn Branchaw wrote:
> > I'm assuming based on the "SSL error&qu
a workaround.
On Thu, Jul 30, 2015 at 11:48 AM, Adrian Klaver adrian.kla...@aklaver.com
wrote:
On 07/30/2015 08:44 AM, Sherrylyn Branchaw wrote:
I was thinking that perhaps an updatable view might do the trick?
Interesting idea! Are you able to get it to work? I keep getting 'ERROR:
cannot copy
my statement
errors out on copying to a view, or inserting an out-of-range timestamp,
when the trigger would resolve all the illegal operations if it just fired
first.
On Thu, Jul 30, 2015 at 5:57 AM, Alban Hertroys haram...@gmail.com wrote:
On 30 Jul 2015, at 2:27, Sherrylyn Branchaw sbranc
Based on your PS asking about data types and commenting that you don't want
to put hour in a separate column, it sounds like this is a brand-new table
you're creating. If so, and if this is a one-time COPY operation, you can
create a text column for the initial import. Then after you're done
