On 07/06/10 06:06, Stephen Frost wrote:
Also, perhaps I'm not being paranoid enough, but all this concern over
error cases really doesn't really worry me that much. The amount of
data one could acquire that way is pretty limited.
It's not limited. It allows you to read all contents of the unde
On Mon, Jun 7, 2010 at 5:42 AM, Andrew Dunstan wrote:
>
> The docs state, w.r.t. $subject:
>
> The password can be provided either in the primary_conninfo string
> or in a separate ~/.pgpass file on the standby server.
>
> I tried this with a database name of "replication" in the .pgpass file,
(2010/06/07 12:06), Stephen Frost wrote:
> * Robert Haas (robertmh...@gmail.com) wrote:
>> Another idea I had was... would it be safe to trust functions defined
>> by the same user who owns the view? If he's granted access to the
>> view and the function to some other user, presumably he doesn't m
(2010/06/07 10:38), Robert Haas wrote:
> On Fri, Jun 4, 2010 at 4:12 PM, Tom Lane wrote:
>> Heikki Linnakangas writes:
>>> On 04/06/10 22:33, Tom Lane wrote:
A counterexample: suppose we had a form of type "text" that carried a
collation specifier internally, and the comparison routine
Hi,
We have codes to change ps display for recovery process during hot standby.
The current code always shows max_standby_delay for the message, but how
about showing actual waiting time instead? Since DBAs can always get the
parameter from postgresql.conf they wrote, so the parameter value itself
* Robert Haas (robertmh...@gmail.com) wrote:
> Another idea I had was... would it be safe to trust functions defined
> by the same user who owns the view? If he's granted access to the
> view and the function to some other user, presumably he doesn't mind
> them being used together? Or is that to
On Thu, May 13, 2010 at 11:00 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> On Thu, May 13, 2010 at 10:52 PM, Tom Lane wrote:
>>> Actually, the lexer translates N'foo' to NCHAR 'foo' and then the
>>> grammar treats that just like CHAR 'foo'. In short, the N doesn't do
>>> anything very useful
On Fri, Jun 4, 2010 at 4:12 PM, Tom Lane wrote:
> Heikki Linnakangas writes:
>> On 04/06/10 22:33, Tom Lane wrote:
>>> A counterexample: suppose we had a form of type "text" that carried a
>>> collation specifier internally, and the comparison routine threw an
>>> error if asked to compare values
The docs state, w.r.t. $subject:
The password can be provided either in the primary_conninfo string
or in a separate ~/.pgpass file on the standby server.
I tried this with a database name of "replication" in the .pgpass file,
which matches what we need to use in pg_hba.conf, but it fail
Hi,
I just spotted that the docs for ALTER TABLE .. DISABLE/ENABLE TRIGGER
are out of date, now that we have deferrable uniqueness and exclusion
constraints.
Also, I think that the original comment in the ENABLE/DISABLE TRIGGER
section was misleading because it suggested that only superusers can
10 matches
Mail list logo
