Thomas Hallgren wrote:
> Is there a way to bypass security checks that retains the SQL parser?
> I'd like my C-code to do something like:
>
> impersonate pgadmin
> SELECT image from class_table
> revert to self
You can use GetUserId() and SetUserId() to flip the current user
identity around as yo
ERROR: column "b" does not exist
ERROR: column "b" does not exist
2 ERROR msg's.
Cause I didn't seen a previous discussion about this, I guess that this could
be a 'particularly only me' problem. The point cames more strange if I grant
that on previous releases (7.4.x) the error msg didn't ca
Tom Lane wrote:
AFAICS you are choosing to do things in the hardest possible way, on
the basis of completely unfounded suppositions about performance gains.
I recommend the KISS principle. Leave the jar files as jars and let the
Java runtime system manage them.
If that was an option, believe me
Peter Eisentraut wrote:
Thomas Hallgren wrote:
Is there a way to bypass security checks that retains the SQL parser?
I'd like my C-code to do something like:
impersonate pgadmin
SELECT image from class_table
revert to self
You can use GetUserId() and SetUserId() to flip the current user
id
Prototype is
#include
int sigwait (sigset_t *set);
but fe_secure.c calls sigwait(&sigpipe_sigset, &signo);
so there's effectively one argument too much!
reards
On Fri, 17 Dec 2004, Tom Lane wrote:
> Date: Fri, 17 Dec 2004 12:49:59 -0500
> From: Tom Lane <[EMAIL PROTECTED]>
> To: Bruce Momjian
Mike G <[EMAIL PROTECTED]> writes:
> It looks like it started off as a permissions problem. I added the
> users to the database before trying again and this time it worked fine.
> I have attached the log from the original attempt if you wish to have a
> look.
As best I can tell, you ran the resto
Thomas Hallgren <[EMAIL PROTECTED]> writes:
> The Java runtime system just does'nt provide a ClassLoader that can be
> made to follow the semantics stipulated by the SQL 2003 Java
> mapping.
[ raised eyebrow... ] Can the spec really be that broken? They don't
write these things in a total vacuum
G u i d o B a r o s i o <[EMAIL PROTECTED]> writes:
> guido=# insert into test1 (b) values (b);
> ERROR: column "b" does not exist
> ERROR: column "b" does not exist
> 2 ERROR msg's.
The postmaster's stderr is pointed at your terminal, so you're getting
the postmaster log output in addition to
Thomas Hallgren <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> You can use GetUserId() and SetUserId() to flip the current user
>> identity around as you like. For such a simple query, however, it
>> might seem better to bypass SPI altogether and do a straight table
>> lookup through
Tom Lane wrote:
Thomas Hallgren <[EMAIL PROTECTED]> writes:
The Java runtime system just does'nt provide a ClassLoader that can be
made to follow the semantics stipulated by the SQL 2003 Java
mapping.
[ raised eyebrow... ] Can the spec really be that broken? They don't
write these things in a to
Tom Lane wrote:
Well, it's not. Exactly what are you going to flip it *to*? You can't
hardwire a particular userid and expect to have a robust solution.
I'd recommend the lower-level approach myself.
How about flipping to the owner of the table, (or perhaps schema since
all pljava specific stuff
On Thu, 2004-12-16 at 17:54, Richard Huxton wrote:
> Josh Berkus wrote:
> >>Clearly, OSDL-DBT2 is not a real world test! That is its benefit, since
> >>it is heavily instrumented and we are able to re-run it many times
> >>without different parameter settings. The application is well known and
> >>
Rémi Zara wrote:
>
> Le 16 d?c. 04, ? 22:48, Bruce Momjian a ?crit :
>
> >
> > I am confused by the threading failure. I don't see any free() call in
> > thread_test.c. Would you go to the tools/thread directory and run the
> > program manually and use a debugger to see the failure line? Is t
OK, I modified the m64k spinlock patch to more cleanly merge into our
code, attached. Applied.
---
Rémi Zara wrote:
> Hi,
>
> Here is a port report for NetBSD 2.0 mac68k, with sources of
> postgresql8.0.0rc1.
>
> Here i
Michael Fuhr wrote:
On Wed, Dec 15, 2004 at 11:41:02AM -0800, Joe Conway wrote:
Just wanted to close the loop for the sake of the list archives. With
Tom's xlog dump tool I was able (with a bunch of his help off-list) to
identify the needed parameters for pg_resetxlog. Running pg_resetxlog
got u
Joe Conway wrote:
> We then spent most of the next 24 hours reviewing the recovered
> database. The bulk data loading process was well instrumented, so we
> knew exactly which data should have been committed prior to the server
> hang, and which files were inprocess (we had been doing 10 loads i
Has anybody tried Solaris8 or 9/ADM64(SUN Fire v40 for example) combo?
I personally don't have access to this platform, but am interested in
someone else has already tried.
--
Tatsuo Ishii
> I have started filling in the supported platform list for the 8.0.0
> release with the information from t
On Sat, Dec 18, 2004 at 02:28:51PM -0800, Joe Conway wrote:
Hi,
> Apparently, either because of the server hang, or because of the flakey
> eth0 interface on reboot, pg_control had become "corrupt". However, it
> was not corrupt in the sense that it contained impossibly invalid data.
> In fact
Alvaro Herrera wrote:
I can't help remembering the fact that the init script executes an
initdb automatically if it finds an empty data directory (the ones I
know of at least -- does the one you are running?). Maybe what happened
was that it found the empty mount point, executed an initdb, and the
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> These values (from the corrupt pg_control file) are strange:
>> pg_control last modified: Tue Dec 14 15:39:26 2004
>> Time of latest checkpoint:Tue Nov 2 17:05:32 2004
The "last modified" date doesn't prove a lot because it wou
Joe Conway <[EMAIL PROTECTED]> writes:
> The Tue Nov 2 17:05:32 2004 seems to be related to the *previous*
> restart; from /var/log/messages:
> Nov 2 17:04:20 csdfds1 syslogd 1.4.1: restart.
> ...
> Nov 2 17:05:22 csdfds1 su: pam_unix2: session started for user
> postgres, service su
> ...
>
Joe Conway <[EMAIL PROTECTED]> writes:
> The manpage for pg_resetxlog gives some general idea how it is used, and
> a way to estimate the next transaction id and wal segment.
I had forgotten that that text was in there. It needs to be updated for
8.0 because WAL segment file names are now three-
Andrew Dunstan schrieb:
I have implemented several requested improvements, which I hope will
prove useful. Since this whole piece of work exists for the benefit of
the pg developers, I'm posting some info here.
The latest version includes these features:
. the log page shows the system type near
Tom Lane wrote:
I think Alvaro's idea that this copy of pg_control got created when the
NFS mount was offline is a real good theory. However, it would seem
that that was quite some time ago (Nov 2 if not earlier), which would
suggest that the mount instability problem has been around longer than
J
Joe Conway wrote:
So one thing I'd strongly suggest is stopping Postgres and dismounting
the NFS server to see what's under there. If there is a valid-looking
PGDATA directory under there, you definitely want to get rid of it to
reduce the risk of this happening again.
Perhaps we should purposef
Reini Urban wrote:
What I also miss is the successful output of the make test step.
Something like the Log in "Details", just behind an additional request.
"Config" =>
Log
Link to "Details"
Without those details one doesn't trust the presented result.
He might think that only the build was succ
Andrew Dunstan wrote:
In the absence of that, in your case, certainly the root-owned
placeholder is a good idea - it seems nicer than disabling on-boot
startup altogether if you can avoid that.
I'm pretty well convinced at this point that a start on boot init script
is inappropriate when working
BTom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > You mean all empty/zero rows can be removed? Can we guarantee that on
> > commit we can clean up the bitmap? If not the idea doesn't work.
>
> For whatever data structure we use, we may reset the structure to empty
> during backend
This relates to an earlier request from someone to allow reporting of
the server start time. It seems both stats start/reset time and server
start time are related.
Is this something for the TODO list? I can't remember why we didn't
want to report server start time, at least for super-users.
-
Is there any chance we could do a little low-risk housekeeping on
contrib in stable branches? Specific low hanging fruit I'd like to see
for the 7.4 branch is adding cube/expected/cube_1.out to the branch, and
backporting the contrib/Makefile changes Tom put in the other day.
(There might be ot
30 matches
Mail list logo
