Andreas Matschewsky ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
PostgrSQL 70 under NT4.0 start postmaster -i & failes
Long Description
I've installed the Postgresql 7.0 under NT Workstation 4.0 Service-Pak 6a using cygwin
Folks,
Please ignore this if you've already fixed these bugs in 7.1 beta 4.
Also, please note that I don't subscribe to the bugs list --- sorry, but
pgsql-sql is all I can keep up with!
BUG REPORT
Version: 7.1 beta 3
Platform: SuSE Linux 7.0
Installation: Mixed; 7.0.3 & 7.1 beta paral
Tom Lane <[EMAIL PROTECTED]> writes:
> You're right, there are multiple levels of parsing going on. The
> string-literal parser gets first crack before the type-specific
> input converter does. If you don't allow for that when counting
> backslashes etc, you'll get confused for sure.
Argh. This
Hello,
I'm writing this as kind of an after thought so I don't have the exact
error message available to me, but I'll try to give you the best information
I can.
The baseline info: Linux 2.4.0 (P200, 32MB Ram, 1.2GB HD) this is the df
output:
Filesystem 1k-blocks U
Hi,
I just found the strange behaviour reported below; I was expecting the
same response from the last two queries...
thanks
Fabio
LONG DESCRIPTION:
A SELECT with regular patterns (~) won't give you the right rows.
CODE SAMPLE:
select version();
-- OUTPUT:
-- vers
Briefly, I create two tables, one having a column which references the
other and which implements cascade deletes and updates. I create a user
who has modify access on one table, but only select on the referenced
table. This user is not allowed to insert a record into the referencing
table - the
Tom Lane ([EMAIL PROTECTED]) wrote:
> I get
>
> FATAL 1: btree: failed to add item to the page in _bt_sort (2)
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the request.
>
> Is that
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Hiroshi Inoue" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, February 08, 2001 4:12 AM
Subject: Re: [BUGS] Problem displaying functions and views in 7.1b3
> Hiroshi Inoue <[EMAIL PROTECTED]
On Sun, Feb 11, 2001 at 12:59:16PM -0500, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > memory leak while using cursors
>
> > DECLARE BOB CURSOR FOR select date_part('epoch', call_time), date_part('hour',
>call_time), date_part('minute', call_time), date_part('dow', call_time), * from
>call_j
Title: jdbc1 & debug
The jdbc1 driver would not compile until I modified Statement.java:
[javac] /usr/src/postgresql-7.1beta4/src/interfaces/jdbc/org/postgresql/jdbc1/Statement.java:284: Missing term.
was:
if (result != null) && ((org.postgresql.ResultSet)result.reallyResultSet())
hello sir, i work on linux and backend as PostgreSQL ver 6.5 and i will be greate ful to u if i would get the solution for a simple question which will be satisfying my needs and the requirements are:1. creating a database in PostgreSQL.2. Inserting the rows for that Table.3. we must write the co
Quoting "Schmidt, Peter" <[EMAIL PROTECTED]>:
> The jdbc1 driver would not compile until I modified Statement.java:
>
> [javac]
> /usr/src/postgresql-7.1beta4/src/interfaces/jdbc/org/postgresql/jdbc1/Statem
> ent.java:284: Missing term.
>
> was:
> if (result != null) &&
> ((org.postgresql
Fabio Nanni <[EMAIL PROTECTED]> writes:
> A SELECT with regular patterns (~) won't give you the right rows.
Strange. I get only 'Zurich' in both cases, as expected, on HP-PA.
Perhaps an Alpha-specific portability problem in the regex code?
Can anyone else duplicate this misbehavior on other pla
"Jake Newren" <[EMAIL PROTECTED]> writes:
> PostgreSQL 7.0.3 installed in the /usr/local/pgsql directory.
> I created a view on my database with the following statement:
> CREATE VIEW wireticket_out AS SELECT wire_tickets.fund_cusip,
> funds.fund_desc, accounts.acct_name, wire_tickets
Under 7.0 you needed update permission on the referenced table to
grab the necessary locks. Under 7.1 you won't need this anymore.
On Thu, 8 Feb 2001, Mike Howard wrote:
> Briefly, I create two tables, one having a column which references the
> other and which implements cascade deletes and up
Fabio Nanni <[EMAIL PROTECTED]> writes:
> A SELECT with regular patterns (~) won't give you the right rows.
Turns out there were some portability problems with our regexp code
on Alphas (or anywhere else that sizeof(int) < sizeof(long)). I've
applied fixes to current CVS; they should be in tomo
16 matches
Mail list logo