Raymond Henick wrote:
> PostGresSQL team:
>
> Hi, I am currently working for a small software company and we are
> unable to find tuning specific documentation for our servers running
> postgres. I know this email is for bug submission however
> if you could direct this email through the pro
Read the COPY manual page. Permissions for COPY are based on the server
user, not the psql user. Try psql \copy.
---
Nahum Castro wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2298
> Logged
On Thu, 2 Mar 2006, Adriaan van Os wrote:
> Tom Lane wrote:
>
> > Adriaan van Os <[EMAIL PROTECTED]> writes:
> >> The manual is simply taking an old prejudice as a fact.
> >
> > No, it is stating a fact as as fact. The existence of one
> > counterexample does not disprove the generalization.
>
>
"Gavin Scott" <[EMAIL PROTECTED]> writes:
> If you rename a primary key, pg_dump tries to recreate it with the original
> name. Here is how to recreate:
>> CREATE TABLE foo ( id integer );
>> ALTER TABLE foo ADD CONSTRAINT foo_pkey PRIMARY KEY (id);
>> ALTER TABLE foo_pkey RENAME TO bar_pkey;
Th
Kashin Oleg wrote:
> My database is with UTF8 encoding. When I use function "upper" for any filed
> of table I get the next error
> "Invalid multibyte character for locale".
Did you select a locale appropiate for UTF8 as well? It's pretty easy
to get into trouble if you select a non-matching pai
The following bug has been logged online:
Bug reference: 2299
Logged by: Gavin Scott
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: fedora core 4
Description:pg_dump error w/ renamed primary keys
Details:
If you rename a primary key, pg
Tom -
Indeed, its entirely possible I forgot to reLOAD the library, especially
given that it appears to work for you with this correction. I'll give it
another go in a clean environment and see how it goes.
Thanks
-Jim
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To:
Bruce Momjian wrote:
This documentation bug has been fixed. We currently have:
=> SELECT * FROM a;
x
---
1 -- no rows in a (0) + 1
(1 row)
=> INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1);
INFO: EXECQ:
The following bug has been logged online:
Bug reference: 2300
Logged by: Kashin Oleg
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Suse 9.1
Description:Error in upper function
Details:
My database is with UTF8 encoding. When I use functi
PostGresSQL team:
Hi, I am currently working for a small
software company and we are unable to find tuning specific
documentation for our servers running postgres. I know this email
is for bug submission however
if you could direct this email through the proper lines I would be very
gratefu
The following bug has been logged online:
Bug reference: 2298
Logged by: Nahum Castro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1
Operating system: Linux Kernel 2.6.22
Description:Bug using copy
Details:
When I try to copy from a file using psql I get
Tom -
Yes, what your suggesting would make sense WRT the ri_triggers however it
doesn't explain the results that are actually appearing using the given code
in the bug report.
If one compiles this code (with or without the missing SPI_finish() call)
the failure still exists. In my opinion
The following bug has been logged online:
Bug reference: 2297
Logged by: bernd
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Linux Fedora Core 3
Description:plpgsql function causes disconnect sometimes
Details:
I'm trying to make some
Tom Lane wrote:
Adriaan van Os <[EMAIL PROTECTED]> writes:
The manual is simply taking an old prejudice as a fact.
No, it is stating a fact as as fact. The existence of one
counterexample does not disprove the generalization.
Keep dreaming. Ignorance rules the world.
Adriaan van Os
14 matches
Mail list logo
