Hello all,
sorry about my english.
I use PostgreSQL-7.2.1 on Linux.
I have a problem to limit Database Access.
I want user X use (ONLY) database Y and user A use (ONLY) database B, and
so on.
Is there another way except use pg_ident.conf ? because i want more
restrictly from pg_ident.co
Dear all,
A simple testing program :
* * * * * * * * * * * * * * begin * * * * * * * * * * * * * * * *
#include
#include
int main (void)
{
unsigned int v;
v = 0x87654321L;
return (0);
}
* * * * * * * * * * * * * * end * * * * * * * * * * * * * * * *
compile with ecpg using :
Hi there,
i have a realy silly question: I installed postgressql (v 7.2) from suse linux
8.0 and then i wanted to try the first steps with it.
As i understood, i shoud login as user postgres an then start the server by
some commands, wich are described in the documents.
It seems, the user pos
This is more, to my mind, a linux question.
But all the same:
su -
# su to root
su - postgres
# once root you can su to postgres without password prompt - and hence (
hopefully ) avoid your problem
then you can run the program - hopefully.
Gareth
-Original Message-
From: [EMAIL PROTE
Hi Wolfgang,
> It seems, the user postgres (group daemons) has been added by the
> installation-procedure -at least not by me. Nevertheless, when i
> try to login
> to this user, it fails because i do not have a password! So i can
> not take
> the very fist step!
>
> So my question simply is: How
Hi all,
Below is the output from 'du -kx /|sort -rn|head'. It's showing that
/var/lib/pgsql/data/base/46169 is using a big chunk of my disk.
How can I tell which DB this is?
What suggestions can people make to reduce the amount of disk space used by
this DB?
__BEGIN__
361365 /
282030 /v
Hi all,
I have a view in this form:
CREATE VIEW my_view AS
< QUERY-A>
UNION ALL
Now if I do:
# explain WHERE login = 'asdadad';
NOTICE: QUERY PLAN:
Nested Loop (cost=0.00..7.08 rows=1 width=88)
-> Nested Loop (cost=0.00..5.05 rows=1 width=52)
-> Index Scan using user_login_lo
Gary Stainburn wrote:
> Hi all,
>
> Below is the output from 'du -kx /|sort -rn|head'. It's showing that
> /var/lib/pgsql/data/base/46169 is using a big chunk of my disk.
>
> How can I tell which DB this is?
> What suggestions can people make to reduce the amount of disk space used by
Alfred Anzlovar wrote:
> Maybe this could/can be done differently, but as it was, it was so easy
> and nice. And if there are more of us, poor souls, with comparable
> problems maybe an option called '--pwd-from-stdin-only' would be a
> solution. Another option (thanks God for Open Source proje
Alfred Anzlovar wrote:
> On Thu, 4 Jul 2002, Bruce Momjian wrote:
>
> > How about PGUSER/PGPASSWORD? That will work. This is assuming you
> > don't have an OS (BSD?) that displays environment variables for a
> > process.
>
> No BSD, Linux. And it works. Thanks.
>
> Well, I must admit we had s
On Thu, 4 Jul 2002, Gaetano Mendola wrote:
> Hi all,
>
> I have a view in this form:
>
> CREATE VIEW my_view AS
> < QUERY-A>
> UNION ALL
>
>
> Now if I do:
>
> # explain WHERE login = 'asdadad';
> NOTICE: QUERY PLAN:
>
> Nested Loop (cost=0.00..7.08 rows=1 width=88)
> -> Nested Loop (cost
We have a need to store text data which typically is just a hundred or so
bytes, but in some cases may extend to a few thousand. Our current field
has a varchar of 1024, which is not large enough. Key data is fixed sized
and much smaller in this same record.
Our application is primarily transa
We hope to use views as a way to give customers odbc based ad-hoc query
access to our database while enforcing security. The reason is that we do
not want to put data into separate tables by customer, but rather use a
customer ID as part of any query criteria on any table.
So the question is:
John Moore wrote:
> We have a need to store text data which typically is just a hundred or so
> bytes, but in some cases may extend to a few thousand. Our current field
> has a varchar of 1024, which is not large enough. Key data is fixed sized
> and much smaller in this same record.
>
> Our a
John Moore wrote:
> We hope to use views as a way to give customers odbc based ad-hoc query
> access to our database while enforcing security. The reason is that we do
> not want to put data into separate tables by customer, but rather use a
> customer ID as part of any query criteria on any ta
>If you don't want a limit, use TEXT. Long values are automatically
>stored in TOAST tables to avoid performance problems with sequential
>scans over long row values.
Thanks...
I wasn't quite clear enough in my question I am focused on OLTP
performance, and in my case the vast majority o
16 matches
Mail list logo
