The following bug has been logged online:
Bug reference: 1013
Logged by: Keith Hankin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Fedora Linux
Description:Authentication doesn't work
Details:
When I start up psql, if I am not not logge
On Wed, 2003-12-17 at 19:57, Tom Lane wrote:
> Mark Shewmaker <[EMAIL PROTECTED]> writes:
> > If a "FOR UPDATE executes before LIMIT" rule stopped the function
> > from ever locking a row, it's still curious why didn't it stop the
> > direct command from ever locking a row as well.
>
>
Your name : Russ Garrett
Your email address : [EMAIL PROTECTED]
System Configuration
-
Architecture (example: Intel Pentium) : P4 Xeon
Operating System (example: Linux 2.0.26 ELF) : Linux 2.4.22 ELF
PostgreSQL version (example: PostgreSQL-7.4)
Hi All,
I am compiling a function that uses the For Query
loopEnd Loop.
I get error "missing ".." at end of SQL expression"
I have read following Note: The PL/pgSQL parser
presently distinguishes the two kinds of FOR loops
(integer or query result) by checking whether the
target variable men
The following bug has been logged online:
Bug reference: 1014
Logged by: vidhya
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.3
Operating system: windows2000
Description:postgres crash
Details:
Hi,
Due to overload postgres crashes often. I am getting the
Hi,
I want to concatenate a it counter to a string in a
loop in plpgsql.
DECLARE
counter integer := 1;
IdSet char : = 'UniqueId'
IdForEachRun varchar;
BEGIN
IdForEachRun := IdSet || counter;(PROBLEM HERE)
--Or IdForEachRun := IdSet + counter;(PROBLEM HERE)
While condition LOOP
Insert into Table
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> When I start up psql, if I am not not logged in as the owner of the database, I get
> the following error message, even if I type the correct password:
> psql: FATAL: IDENT authentication failed for user "keith"
This is not a bug: it's the way
Mark Shewmaker <[EMAIL PROTECTED]> writes:
> On Wed, 2003-12-17 at 19:57, Tom Lane wrote:
>> Mark Shewmaker <[EMAIL PROTECTED]> writes:
>>> If a "FOR UPDATE executes before LIMIT" rule stopped the function
>>> from ever locking a row, it's still curious why didn't it stop the
>>> direct command fro
I should play with your code, but I'm lazy.
1) lmfpLimit integer ALIAS for $3
is missing the trailing ";"
lmfpLimit integer ALIAS for $3;
2) VARCHAR variables need a length
curId varchar;
should be
curId varchar(100);
3) I have not seen this style of declaration, where the argum
"Russell Garrett" <[EMAIL PROTECTED]> writes:
> Constraints are being weird. The reproduction instructions speak for
> themselves.
You haven't really provided enough info to let anyone do anything about
this. Certainly no one else is going to be able to reproduce the
problem based on what you've
Puneet Paul <[EMAIL PROTECTED]> writes:
> DECLARE
> curTrackList char(15) ALIAS for $1;
> sliceFile varchar ALIAS for $2;
> lmfpLimit integer ALIAS for $3
> mTrackDet RECORD;
If that's an accurate copy of your function, then the problem is likely
the lack of a semicolon on
Neil Conway <[EMAIL PROTECTED]> writes:
> Okay, I've attached a patch that fixes the problem for me. The problem
> turned out to be pretty simple: the PostgreSQL code (both backend and
> frontend SSL support) was calling SSL_get_peer_certificate() without
> properly free'ing its return value.
Appl
The following bug has been logged online:
Bug reference: 1015
Logged by: Aarjan Langereis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.4
Operating system: RedHat Linux 9 kernel 2.4.20-20.9
Description:Got a signal 11 while trying to create a temp table
Det
Tom Lane wrote:
> "Russell Garrett" <[EMAIL PROTECTED]> writes:
>> Constraints are being weird. The reproduction instructions speak for
>> themselves.
>
> You haven't really provided enough info to let anyone do anything
> about this. Certainly no one else is going to be able to reproduce
> the pr
>> 2. The index is corrupt, possibly due to a hardware glitch. (This
>> seems unlikely because the SELECT result appears normal, but I can't
>> rule it out entirely.)
>
> We had a table error a few weeks back, however we re-imported the
> table from scratch. So it may well be this. I doubt it's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I get error "missing ".." at end of SQL expression"
...
> Can someone help please
The problems appear to be in your declare block:
> curTrackList char(15) ALIAS for $1;
> sliceFile varchar ALIAS for $2;
> lmfpLimit integer ALIAS for $3
Y
Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > Okay, I've attached a patch that fixes the problem for me. The problem
> > turned out to be pretty simple: the PostgreSQL code (both backend and
> > frontend SSL support) was calling SSL_get_peer_certificate() without
> > properly free'i
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> I tried to create a temp table and got my back-end restarting because of a signal 11.
Hmm. Can you get a debugger backtrace from the core dump?
> It seems to me, and please correct me if I’m wrong, that there is a limit to the
> size that a j
"Russell Garrett" <[EMAIL PROTECTED]> writes:
> last=> reindex index profile_pkey;
> ERROR: could not create unique index
> DETAIL: Table contains duplicated values.
Okay, it looks like the table actually contains duplicate rows but the
index has managed to lose track of that fact. You can see
19 matches
Mail list logo
