Well here's the thing. Before i was trying to use ShmemInitStruct in
buf_init.c. The problem with this is that you can't shrink or grow shared
memory. That is why i switched over and just used malloc. So i seem to be
in a big dilemma, on one hand, if i use malloc, i can't keep this info i
need; and
Nailah Ogeer <[EMAIL PROTECTED]> writes:
> So what is happening is that i enter the relation ids into the BP cluster
> linked list fine and every time i call psql, it automatically deletes.
Sounds to me like you are trying to keep stuff in backend-local memory
that needs to be in shared memory.
what i was trying to do was maintain an array of Buffer pool clusters.
What i did previously was change the pointers around in the freelist so
instead of one i have 4. Now each buffer pool is called a BP cluster.
Within this BP cluster i have things like cluster id, freelist descriptor
etc, and a l
On Thu, Jun 19, 2003 at 17:07:43 -0400,
Nailah Ogeer <[EMAIL PROTECTED]> wrote:
Please don't respond to other messages to start a new thread.
> What i am trying to do is to maintain a linked list of all the relations
> in a database. When i create a db then i want it to insert into the linked
>
"Colin 't Hart" <[EMAIL PROTECTED]> writes:
> Does postgres have a concept of a 'root' user? Then the password should
> only be prompted when one isn't root; ie. adopt Unix semantics.
Can't really do that in psql's \c, since it's establishing a whole new
connection; there is no possibility for su
Tatsuo Ishii:
> As you can see, psql reconnect as any user if the password is same as
> foo. Of course this is due to the careless password setting, but I
> think it's better to prompt ANY TIME the user tries to switch to
> another user. Comments?
Does postgres have a concept of a 'root' user? T
