Please don't remove the list from the recipients. Added back.
> This was on my Windows XP. I never installed Postgresql
> before on this computer. I do not know which account it was, since
>
> > >> Internal account lookup failure: No mapping between
> > accound names and
> > >> security IDs wa
Patch applied to version 8.1. Large query now runs in seconds.
Thanks Tom. Regards, Matt Carter
Tom Lane wrote:
"Ferindo Middleton" <[EMAIL PROTECTED]> writes:
This bug report involves more than one proposed bug. I work at a federal
government agency. The information technology division at this agency
refuses to allow the database version 8.0.4 on their network because of
several securi
The following bug has been logged online:
Bug reference: 2063
Logged by: neeraj chaudhari
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.4
Operating system: Red Hat linux 9.0
Description:Unsupported frontend protocol
Details:
Hi,
i have recently installed
TODO has:
o Add ON COMMIT capability to CREATE TABLE AS ... SELECT
---
David Fetter wrote:
> On Thu, Nov 17, 2005 at 05:32:43PM -0500, Tom Lane wrote:
> > David Fetter <[EMAIL PROTECTED]> writes:
> > > On Thu, Nov 1
On Tue, Nov 22, 2005 at 06:20:37PM -0500, Bruce Momjian wrote:
>
> TODO has:
>
> o Add ON COMMIT capability to CREATE TABLE AS ... SELECT
Great :)
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 415 235 3778
Remember to vote!
---(end o
"Harald Armin Massa" <[EMAIL PROTECTED]> wrote
>
> 2005-11-21 09:45:50 ERROR: could not open relation 1663/17253/43471: No
> such
> file or directory
>
> My checking showed that... within directory data/base/17253 there is
> indeed
> no file named 43471; but ones named 43470,43472,43473 .
>
""neeraj chaudhari"" <[EMAIL PROTECTED]> wrote
>
> FATAL: unsupported frontend protocol
> FATAL: unsupported frontend protocol
> FATAL: unsupported frontend protocol
>
> Then to i am able to connect to the database & access & modify the
> records.
>
It looks like your client guesses out the r
Folks,
Having blank lines in -f scripts was causing silent failures. This
fixes it, for some value of "fixes." If it's OK, please apply to 8.1
CURRENT and CVS TIP :)
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 415 235 3778
Remember to vote!
Index: contrib/pgbench/
The following bug has been logged online:
Bug reference: 2066
Logged by: apco
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows XP with sp2
Description:installer error: code 2755.
Details:
Postgresql MUI wrapper: can't find specified
The following bug has been logged online:
Bug reference: 2065
Logged by: Wim Audenaert
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0.2
Operating system: Windows XP
Description:Problem with language conversion in pg_dump
Details:
I have a database create
The following bug has been logged online:
Bug reference: 2064
Logged by: tr
Email address: [EMAIL PROTECTED]
PostgreSQL version: 1.2.1
Operating system: windows
Description:retrieving more the 6 columns from a table via c#
Details:
I'm trying to run a simple select
"Wim Audenaert" <[EMAIL PROTECTED]> writes:
> When I try to do a pg_dump of my database, I get the following error
> message:
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: cache lookup failed for function
> 17039
I'm not sure how you managed that, but I'm sure that i
"Wim Audenaert" <[EMAIL PROTECTED]> writes:
> When I create a new database, this function (oid 17039 and used for utf8
> translation) is not defined in the pg_proc table. I tried to create a new
> database. The pg_proc table contains several functions, but not this one.
Hmm, I see that utf8_to_t
If I create a normal table and a normal view that queries that table I
get incorrect results when I query the view using the AS alias in the
select statement. For example, if I create the following objects:
CREATE TABLE Test1( col1 VARCHAR(200) );
CREATE VIEW Test2 AS SELECT col1 FROM Test1 ORDER
Quingqing,
no, it is definitely NOT a temp table. I know which table it is, because:
that "could not open relation ..." error message was exactly provokable
with "select * from repofeld", which is one of my tables in that
database.
(And that was the way it was passed on to me: my application put
Also forgot to mention that this only started occuring in PostgreSQL 8.1. Here is my SELECT version() output:
version
---
PostgreSQL 8.1.0 on i686-r
17 matches
Mail list logo