Dear All,
I have made a trigger procedure that logs all table's changes to the
log_table in XML format, but i do need to log a user who did that and
not succsessful with this.
The documentation (including "37.10. Trigger Procedures") give me nothing.
Could somene supply me with a solution or docu
On Tue, Jul 06, 2004 at 15:44:01 -0700,
[EMAIL PROTECTED] wrote:
> Hi there,
>
> I am using Postgresql 7.3 and I want to grant select rights to a user on all tables
> in a schema, including those that may be created in the future but whose names are
> not yet known. I want to do something lik
you should check the logs, when postmaster dies right after starting it always leaves a helpfull message there.
On Wed, 2004-07-07 at 10:09, José Augusto Tovar wrote:
Hi all,
I´m using postgreSQL in WinME and i had a very strange problem. When i start
the postgres the process postmaster sta
Ok, I've tried a number of things here and I know I'm missing something but at
this point my head is spinning (i.e. lack of sleep, too much coffee, etc...)
My environment is PG 7.4.3 on Linux with 512Mb of ram and swap. This was just
upgraded from 7.4 (just to make sure I'm current). Some of my
Keith C. Perry wrote:
I have a table with with 1 million records in it. Here is the definition
CREATE TABLE report
(
match int4,
action varchar(16),
stamp timestamptz,
account varchar(32),
ipaddress inet,
profile varchar(16),
rating text,
url text
)
WITHOUT OIDS;
The is one index
This is a really trivial question, but I'm curious. Why do
subselects in target lists behave differently than simple queries?
Ex:
[lexus] create temporary table bar (key varchar(32) not null);
CREATE TABLE
[lexus] insert into bar select '';
INSERT 1319585 1
[lexus] insert into bar select (select
Anton Nikiforov wrote:
Dear All,
I have made a trigger procedure that logs all table's changes to the
log_table in XML format, but i do need to log a user who did that and
not succsessful with this.
The documentation (including "37.10. Trigger Procedures") give me nothing.
Could somene supply me
Thanks for the replay, Richard.
Richard Huxton wrote:
Anton Nikiforov wrote:
Dear All,
I have made a trigger procedure that logs all table's changes to the
log_table in XML format, but i do need to log a user who did that and
not succsessful with this.
The documentation (including "37.10. Trigger
Quoting Richard Huxton <[EMAIL PROTECTED]>:
> Keith C. Perry wrote:
> >
> > I have a table with with 1 million records in it. Here is the definition
> >
> > CREATE TABLE report
> > (
> > match int4,
> > action varchar(16),
> > stamp timestamptz,
> > account varchar(32),
> > ipaddress
digest-status LISTNAME
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Anton Nikiforov wrote:
Could somene supply me with a solution or documentation part that i
should read?
Can't remember which part it is, but you want one of:
SELECT CURRENT_USER;
SELECT SESSION_USER;
test=# SELECT CURRENT_USER;
current_user
--
anton
(1 row)
test=# SELECT SESSION
set pgsql-general digest
---(end of broadcast)---
TIP 8: explain analyze is your friend
Ok - just to end this thread, I think I understand what I was missing.
I'll stop this thread, and just comment on my first thread.
Thank you everyone who helped
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an inde
> There's a good bit of depth in the archives of this list. I would start
> searching back for discussions of effective_cache_size, as that is
involved
> in *costing* the caching job that the OS is doing.
Thanks - that's just what I need to sink my teeth into. I'll have a trawl
and get back later
Hello Shridhar,
Thanks for the reply.
> There is no reason why you should not do it. How remains to be a point of
> disagreement though. You don't allocate 16GB of shared buffers to
postgresql.
> That won't give you performance you need.
I think in the other thread, Tom was alluding to this too.
> I get the feeling that, that regardless 64bit support or not, that the
> *concept* of a database which just happens to all easily fit within RAM
> isn't one that gets the thumbs down...
Oops, I meant to say '*is*' one that gets the thumbs down...
---(end of broadcast)-
Hello again Mike,
Thanks for the replies! Here's my next salvo!
> Perhaps I'm a bit naive about complex data structure caching strategies,
but
> it seems to me that the overhead of tracking tuples (which is what you
> would want if you are going to manage your own cache, as opposed to simply
> ca
>If all the data fits into memory, then this cache thrashing won't occur,
yes?
No - it *can* occur in a 2 tier cache strategy.
The critical question here is: *If* the data postgresql needs is in the
linux buffer cache, what (if anything) does the OS have to do to make it
available to the postmas
> It's not that making the cache bigger is inefficient, it's that the cache
is
> not used the way you are thinking.
Ok, I think I've got it now. The missing piece of the puzzle was the
existence of the Linux buffer cache. So that's what the
effective_buffer_cache value is for(!)
I read Shridhar
Hello again and thanks to everyone for the replies so far.
Tom, and all, I hear what you are all saying, and furthermore, in cases
where the amount of RAM is much smaller than the database size, I agree
totally. However, I'm *only* talking about a particular scenario which, till
now, has really on
We're developing a java app and are using postgres as the database. On
our dev server I started the app, closed it, but the java process was
still open so I killed it, which caused the above error. I've had to do
this in the past but have not had this happen before. I've searched the
archives a
Hi,
I tried to install phpopenchat but I can't create this table:
poc=> CREATE TABLE poc_user_account (
poc(> USER varchar(255) NOT NULL,
poc(> PASSWORD varchar(255),
poc(> CONFIRM_CODE char(32),
poc(> DISABLED int NOT NULL DEFAULT '0',
poc(> KICKED int NOT NULL DEFAULT '0',
poc(> PAS
22 matches
Mail list logo
