On 24/11/05 5:27 pm, "Adam Witney" <[EMAIL PROTECTED]> wrote:
> On 24/11/05 5:28 pm, "Tom Lane" <[EMAIL PROTECTED]> wrote:
>
>> Adam Witney <[EMAIL PROTECTED]> writes:
>>> Does this help identifying what went wrong?
>>
>> At this point I think there's no question that your filesystem is
>> dropp
Hi,
As a superuser I created a normal user:
CREATE USER probauser NOCREATEDB NOCREATEUSER;
ALTER GROUP eden_users ADD USER probauser;
a function:
CREATE OR REPLACE FUNCTION edenproc_usesysid(text)
RETURNS int4 AS .
-- Note that the owner of this
Could it be faulty hardware?
Run memtest86? Test your drives?
At 10:49 AM 11/26/2005 +, Adam Witney wrote:
Any ideas what is going on here?
Thanks again for any help
Adam
---(end of broadcast)---
TIP 6: explain analyze is your friend
Adam Witney <[EMAIL PROTECTED]> writes:
> pg_dump: ERROR: unexpected chunk number 5153 (expected 21) for toast value
> 245334402
> measured_bioassay_base is always inserted at the same time as mba_data_base
> (the table where I had the problem before) and it has a text field which is
> very large
=?iso-8859-2?Q?Egy=FCd_Csaba?= <[EMAIL PROTECTED]> writes:
> # select edenproc_usesysid('probauser');
> ERROR: function edenproc_usesysid(text) does not exist
^^
Read the error message: this is not a lack-of-permissions problem.
I'd wonder w
On 26/11/05 4:14 pm, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> Adam Witney <[EMAIL PROTECTED]> writes:
>> pg_dump: ERROR: unexpected chunk number 5153 (expected 21) for toast value
>> 245334402
>
>> measured_bioassay_base is always inserted at the same time as mba_data_base
>> (the table where I h
Adam Witney <[EMAIL PROTECTED]> writes:
> I deleted the two datasets in mba_data_base that were affected by the empty
> pages, I also deleted the relevant two rows in measured_bioassay_base... But
> maybe it didn't do the right thing with the toast table for these two rows?
Evidently the missing d
Hi, it seems to be some kind of windows/pgadmin error (?), because running
the dump on the linux server it was ok.
I was able to work around the problem, but...
Thank you Jaime.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jaime Casanova
Sent: Frida
Hi Tom,
thank yor answer.
>Read the error message: this is not a lack-of-permissions problem.
You are right, I just meant that perhaps it needs some other settings, e.g.
set search_path or similar ... Sorry for that...
Regarding the search_path it is the same in both cases:
# show search_path;
=?iso-8859-2?Q?Egy=FCd_Csaba?= <[EMAIL PROTECTED]> writes:
> Regarding the search_path it is the same in both cases:
> # show search_path;
> search_path
> --
> $user,public
> (1 row)
That's not "the same" if the superuser has a self-named schema ...
regards,
On Sat, Nov 26, 2005 at 06:13:21PM +0100, Egyd Csaba wrote:
> Regarding the search_path it is the same in both cases:
>
> # show search_path;
> search_path
> --
> $user,public
> (1 row)
For different users, the above represents *different* search paths
because $user is expanded to t
Take a loot at postfix's proxymap feature - I believe it works for MySQL
and Postgres, and may solve your problem.
http://www.postfix.org/proxymap.8.html
From the docs
"To consolidate the number of open lookup tables by
sharing one open table among multiple processes.
For example, making m
Bj?rn T Johansen wrote:
> I am upgrading from 7.4 to 8.1 and there seems to have been a change
> in how postgresql log prepared sql statements.. Before I could see the
> actual statements (i.e. after every parameters had been changed with
> real values) but now I see the sql statements before the c
Of course, RTFM. :) Thanks for the pointer. I'll pursue that path and see how it goes.
Thanks,
Greg
On Sat, 2005-11-26 at 17:41 +, John Sidney-Woollett wrote:
Take a loot at postfix's proxymap feature - I believe it works for MySQL
and Postgres, and may solve your problem.
http://www.
on 11/24/05 9:55 AM, [EMAIL PROTECTED] purportedly said:
> Hi Jaime. I currently work with psycopg with web apps. My question is
> more a matter of whether postgres can be installed in a way that keeps
> it contained to the program files for the app (as opposed to the
> regular type of install wh
Tom, I see your point and you are right.
Michael, it seems if no functions were in my database...
When I created the moson.gdb database I didn't create any additional
schemas. I simply reloaded the dump - I think into the public. Thats all.
In PgAdmin the (all my) functions can be seen in the
On Sat, Nov 26, 2005 at 09:10:40PM +0100, Egyd Csaba wrote:
> moson.gdb=> \df eden*
>List of functions
> Schema | Name | Result data type | Argument data types
> +--+--+-
> (0 rows)
Oops, I forgot that \df uses pg_function_is_vis
-Original Message-
From: Együd Csaba (Freemail) [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 26, 2005 9:36 PM
To: 'Michael Fuhr'
Subject: RE: [GENERAL] GRANT question
OK, here you are.
---
moson.gdb=> SELECT oid::regprocedure FROM pg_proc WHERE proname IL
On Sat, Nov 26, 2005 at 09:37:00PM +0100, Egyd Csaba (Freemail) wrote:
> moson.gdb=> SELECT oid::regprocedure FROM pg_proc WHERE proname ILIKE
> '%eden%';
[...]
> public.edenproc_usesysid(text)
Hmmm...so the function indeed exists in the public schema. What
happens if you call the schema-qualifi
Michael Fuhr <[EMAIL PROTECTED]> writes:
> Oops, I forgot that \df uses pg_function_is_visible(), so it won't
> show functions that aren't in your search path. Try this:
Or try
\df *.edenproc_usesysid
I note the lack of "show search_path" for the non-admin user in
your example ... it mig
Hi Tom,
in case of the admin it results: {pg_catalog,public}. In case of the
non-admin user: {pg_catalog}!!!
Again, seeing it from the PgAdmin (as both users) I can see all the 5 well
known schemas.
-- csaba
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Sunday, Novemb
=?iso-8859-2?Q?Egy=FCd_Csaba?= <[EMAIL PROTECTED]> writes:
>> ... it might also be interesting to try
>> select current_schemas(true);
> in case of the admin it results: {pg_catalog,public}. In case of the
> non-admin user: {pg_catalog}!!!
I think that confirms Michael's suggestion that you'
Dear Michael, Tom,
thak you very much! Now it works well.
moson.gdb=> SELECT public.edenproc_usesysid('probauser');
ERROR: permission denied for schema public
moson.gdb=> select current_schemas(true);
current_schemas
-
{pg_catalog}
(1 row)
moson.gdb=# GRANT USAGE ON SCHEMA PUB
23 matches
Mail list logo
