Hello,
Is there are way to determine a subject?
Thanks.
--
// Dmitriy.
For clarity, is it possible to write a SECURITY DEFINER function which
returns a value of current_user at the moment of call?
2013/12/4 Dmitriy Igrishin
> Hello,
>
> Is there are way to determine a subject?
>
> Thanks.
>
> --
> // Dmitriy.
>
>
--
// Dmitriy.
Hello
pls, try session_user
Regards
Pavel
2013/12/4 Dmitriy Igrishin
> Hello,
>
> Is there are way to determine a subject?
>
> Thanks.
>
> --
> // Dmitriy.
>
>
2013/12/4 Pavel Stehule
> Hello
>
> pls, try session_user
>
Not really :-(. The user can perform SET ROLE before calling the SECURITY
DEFINER function and I need to know who is the caller at the time of call.
I need something like a calling_user() function...
--
// Dmitriy.
In other words, I need to get an information about *current* role of the
caller
inside the SECURITY DEFINER function.
2013/12/4 Dmitriy Igrishin
>
>
>
> 2013/12/4 Pavel Stehule
>
>> Hello
>>
>> pls, try session_user
>>
> Not really :-(. The user can perform SET ROLE before calling the SECURITY
Shuwn Yuan Tee wrote:
> We recently experienced crash on out postgres production server. Here's our
> server environment:
>
> - Postgres 9.3
> - in OpenVZ container
> - total memory: 64GB
>
>
> Here's the error snippet from postgres log:
>
> ERROR: could not read block 356121 in file "base/33
HI all,
Is anyone aware of cases where psql will occasionally return an exit status
of 1, despite there being no obvious error condition?
I have a regular (daily) cron that executes a fairly simple script of the
form:
> psql --set ON_ERROR_STOP=1 -h $DB_HOST -U $DB_USER -a -v DATE="'${DATE}'" -
I should have mentioned, psql client and server version 9.2.4
From: Tim Kane
Date: Wednesday, 4 December 2013 10:59
To: pgsql-general General
Subject: unexplainable psql exit status 1
HI all,
Is anyone aware of cases where psql will occasionally return an exit status
of 1, despite there
Tim Kane wrote:
> Is anyone aware of cases where psql will occasionally return an exit status
> of 1, despite there being
> no obvious error condition?
>
> I have a regular (daily) cron that executes a fairly simple script of the
> form:
>
> psql --set ON_ERROR_STOP=1 -h $DB_HOST -U $DB_U
> According to the documentation you quoted, it would be useless to set
> log_statement=all, because the problem is on the client end.
>
> Shell debugging sounds slightly more promising, but it will probably
> not tell you much more than that psql returned with exit code 1.
>
> A quick look at t
Tim Kane wrote:
> I’ve enabled shell debugging to be 100% sure that I’m not munging the return
> code anywhere. It’s
> entirely possible there is something going on at the shell side of things,
> though I fail to see how
> just at the minute :)
> The output of the script is as follows, bearing in
On Tue, Dec 3, 2013 at 4:04 PM, john gale wrote:
> Does this suggest that VACUUM FULL needs free disk space on the order of
> the full size of the table that it's vacuuming to be able to complete? Or
> does it / can it write the filesystem files in the 1GB chunks stored in
> /base while removing
Albe Laurenz wrote:
> Shuwn Yuan Tee wrote:
>
>> We recently experienced crash on out postgres production server.
>> Here's our server environment:
>> - in OpenVZ container
>> ERROR: could not read block 356121 in file "base/33134/33598.2": Bad address
>>
>> LOG: server process (PID 21119) was
Hi,
I need some help with upsert.
Some info on what I want to do:
Each day I create a table for my firewall logs. I have one entry for
one occurrence of all the field except sum, which is the number of
occurrence I have of each log that match all the field. My table has the
f
Hi,
> ERROR: column reference "firewall" is ambiguous
> LINE 3: ... a WHERE NOT EXISTS (SELECT * FROM upsert b WHERE b.firewall...
set firewal = misses a table
HTH
Kind regards/met vriendelijke groet,
Serge Fonville
http://www.sergefonville.nl
2013/12/4 Eric Lamer
> Hi,
>
>
>
>I nee
LINE 3: ... a WHERE NOT EXISTS (SELECT * FROM upsert b WHERE b.firewall...
As you can see it is b.firewall where b is alias to table upsert. That's
why I don't understand the error.
From: Serge Fonville [mailto:serge.fonvi...@gmail.com]
Sent: December 4, 2013 12:53 PM
To: Eric Lamer
On Tue, Dec 3, 2013 at 2:04 PM, john gale wrote:
>
> Due to running low on disk space, we have recently removed a majority of rows
> from a table to an archival DB.
>
> Although VACUUM allows disk space to be re-used, VACUUM FULL is the only one
> that actively reclaims disk space for use by the
Le mercredi 04 décembre 2013 à 17:48 +, Eric Lamer a écrit :
>
>
> Each day I want to copy the last 7 days into one table so I have one
> table with the last 7 days of logs.
>
>
>
> So I want to copy the data from 7 tables into 1. If the row does
> not exist I just insert and if
On Tue, Dec 3, 2013 at 4:32 AM, Shuwn Yuan Tee wrote:
> We recently experienced crash on out postgres production server. Here's our
> server environment:
>
> - Postgres 9.3
> - in OpenVZ container
> - total memory: 64GB
>
>
> Here's the error snippet from postgres log:
>
> ERROR: could not read b
Readers,
Can postgresql be deployed with audit trail and data validation
capability, to meet compliance with 21 cfr part 11?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 12/4/2013 3:34 PM, e-letter wrote:
Can postgresql be deployed with audit trail and data validation
capability, to meet compliance with 21 cfr part 11?
IMHO, that sort of audit trail should be higher level in your business
logic, not in the database. but that's just my opinion, worth exact
On 12/04/2013 04:41 PM, John R Pierce wrote:
On 12/4/2013 3:34 PM, e-letter wrote:
Can postgresql be deployed with audit trail and data validation
capability, to meet compliance with 21 cfr part 11?
IMHO, that sort of audit trail should be higher level in your business
logic, not in the datab
Hi,
I need some help with upsert.
Some info on what I want to do:
Each day I create a table for my firewall logs. I have one entry for
one occurrence of all the field except sum, which is the number of
occurrence I have of each log that match all the field. My table has the
f
I have built big nationwide health databases, and other secure systems
requiring traceback and auditability.
The more you are able to make the required processes transparent to the
end user, the happier they are and the fewer problems you have from a
user acceptance perspective.
Audit does b
Hello,
On Dec 4, 2013, at 12:39 PM, Eric Lamer wrote:
> Hi,
>
>I need some help with upsert.
>
>Some info on what I want to do:
>
>Each day I create a table for my firewall logs. I have one entry for one
> occurrence of all the field except sum, which is the number of occur
On Wed, Dec 4, 2013 at 9:15 PM, Robin wrote:
> I have built big nationwide health databases, and other secure systems
> requiring traceback and auditability.
>
> The more you are able to make the required processes transparent to the end
> user, the happier they are and the fewer problems you have
26 matches
Mail list logo
