ndefined behavior in
the first statement).
Or it should raise some kind of warning, e.g. "you're using
undocumented/unsupported/deprecated/broken syntactic sugar".
Denis
On Jun 12, 2013, at 12:05 PM, Greg Stark wrote:
> On Wed, Jun 12, 2013 at 9:58 AM, wrote:
>> de
В Срд, 07/11/2012 в 11:48 -0500, Tom Lane пишет:
> Denis Feklushkin writes:
> > in 9.2.0:
> > PQsendQueryParams() with multiple command statement (like "select 123;
> > select 456") unexpectedly causes error:
>
> > "cannot insert multiple commands i
in 9.2.0:
PQsendQueryParams() with multiple command statement (like "select 123;
select 456") unexpectedly causes error:
"cannot insert multiple commands into a prepared statement."
But PQsendQuery() works fine.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
Hi!
Bug reporting form:
http://www.postgresql.org/support/submitbug/
is not works - it slows down and fails with "CSRF verification
failed" (in google chrome, at least)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresq
gt;you want.
here you are right also, because it seems now, that if "order by id" is missing
then data results of a query could vary depending on changes to a
record done(or other
algorythms).
Lets close this bug.
With deep respect,
Denis Kolesnik.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
conclude
not without a reason that the queries different on presense or absense
"...limit 2 offset 2..." should return results which are consistent.
Basing on this I conclude, that it is a bug.
With respect,
Denis Kolesnik.
On 8/22/12, Kevin Grittner wrote:
> Denis Kolesnik wrot
I have now VERY strong argument to consider it is as a bug:
if there a understandable for SQL language sequence which sorts
in other fashion when adding "LIMIT".
I did try the same with a last name starting with "G" (there also more
than one entry with identical surnames) and it worked ok(the res
I only did some cursory tests, but the patch (applied to Macport's beta2
distribution) seems to be working on my dev box (OSX / Snow Leopard).
I'll report back if I run into oddities further down the road.
Thanks a lot!
Denis
>
>From: Je
Wrapping apparently doesn't want to work in expanded mode...
Lengthier discussion here:
http://stackoverflow.com/questions/6306063/
test=# \t
Showing only tuples.
test=# \pset border 0
Border style is 0.
test=# \pset format wrapped
Output format is wrapped.
test=# \pset columns 20
Target width
Пересылаемое сообщение
От: Denis Feklushkin
Кому: sub...@bugs.debian.org
Тема: ERROR: cannot extract system attribute from minimal tuple
Дата: Sat, 05 Feb 2011 09:50:06 +0700
Package: postgresql-9.0
Version: 9.0.3-1
Severity: normal
Tags: upstream
Query:
SELECT currency_id1
The following bug has been logged online:
Bug reference: 5749
Logged by: Denis
Email address: dolgalevde...@mail.ru
PostgreSQL version: 9.0.1
Operating system: Windows XP
Description:Case sensivity of names of sequences.
Details:
Hello.
I found some problem with
The following bug has been logged online:
Bug reference: 4680
Logged by: Denis Afonin
Email address: v...@itkm.ru
PostgreSQL version: 8.3.6
Operating system: Linux Debian Lenny
Description:Server crashed if using wrong (mismatch) conversion
functions
Details:
I do
2009"
good_date_13: "27 12 2008"
good_date_12: "28 12 2008"
bad_date_11 : "29 12 2009"
bad_date_10 : "30 12 2009"
bad_date_9 : "31 12 2009"
good_date_8 : "01 01 2009"
good_da
The following bug has been logged online:
Bug reference: 4562
Logged by: Denis Monsieur
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: Debian etch
Description:ts_headline() adds space when parsing url
Details:
My system is 8.3.4, but
Hi!
The reason was a corrupted system library and "sfc /scannow" have helped me.
I wish you remember this solution and will advise it to other people.
Thanks.
--- Исходное сообщение ---
От кого: Zdenek Kotala <[EMAIL PROTECTED]>
Кому: [EMAIL PROTECTED]
Дата: 1 сентября, 19:55
Hi.
Thanks for fast reply!
I had always completely removed Postgre before each try of installing (file
system, system services).
I have tried your advice and, of course, it did not help.
Seems like some windows update made critical for Postgre changes in windows
system libraries, us
Hello All.
I want to output result of query with double newline record separated.
For example:
psql -At -P recordsep="\n\n" -U postgres -c "select generate_series(1,3)"
1
2
3
But my result is:
psql -At -P recordsep="\n\n" -U postgres -d chronopay -c "select
generate_series(1,3)"
1
The following bug has been logged online:
Bug reference: 2752
Logged by: Denis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5
Operating system: Gentoo 2006.1 server x86
Description:Website bug
Details:
Don't know where to file this bug, but w
The following bug has been logged online:
Bug reference: 2438
Logged by: MATTASOGLIO DENIS
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: WINDOWS XP
Description:error connect with odbc
Details:
Hello world
i work with powerbuilder odbc
Pardon if I insist, but accepting data that contradicts an external key
contraint without raising an error is a bug and by no means a feature.
Denis
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 10, 2006 11:35 PM
> To: Denis de B
via drop_domain
3. triggers cascade delete on domains
via foreign key
4. rewritten as do nothing <-- missing integrity check and/or rollback here
via public_domain_delete_protect (things work fine without this step)
Best,
Denis
postgresql-bug.sql
Description: Binary data
---
On Wednesday 13 July 2005 17:43, Tom Lane wrote:
> Denis Vlasenko <[EMAIL PROTECTED]> writes:
> > Consider my posts in this thread as user wish to
> > * libpq and network protocol to be changed to allow for incremental reads
> > of executed queries and for multi
On Monday 11 July 2005 03:38, Alvaro Herrera wrote:
> On Sun, Jul 10, 2005 at 01:05:10PM +0300, Denis Vlasenko wrote:
> > On Thursday 07 July 2005 20:43, Alvaro Herrera wrote:
>
> > > Really? I thought what really happened is you had to get the results
> > > on
On Thursday 07 July 2005 20:43, Alvaro Herrera wrote:
> On Thu, Jul 07, 2005 at 08:17:23AM -0700, John R Pierce wrote:
> > Neil Conway wrote:
> > >Denis Vlasenko wrote:
> > >
> > >>The same php script but done against Oracle does not have this
> > >
On Thursday 07 July 2005 08:54, Neil Conway wrote:
> Denis Vlasenko wrote:
> > Symptom: even the simplest query
> > $result = pg_query($db, "SELECT * FROM big_table");
> > eats enormous amounts of memory on server
> > (proportional to table size).
>
> Ri
On Wednesday 06 July 2005 16:52, Harald Armin Massa wrote:
> Denis,
>
> $result = pg_query($db, "SELECT * FROM big_table");
>
> you are reading a big result (as I suspect from big_table) into memory. It
> is perfectly normal that this uses large amounts of memory.
The following bug has been logged online:
Bug reference: 1756
Logged by: Denis Vlasenko
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Linux
Description:PQexec eats huge amounts of memory
Details:
Verbatim from http://bugs.php.net
On Sun, 11 Jan 2004, Peter Eisentraut wrote:
PE> Denis N. Stepanov wrote:
PE> > snprintf()/vsnprintf() functions are not ANSI-compliant
PE>
PE> Yes, they are.
Sorry, I was talking about ANSI X3.159-1989, which certainly does not declare
snprintf(). In practice it is diffucult t
hange is
inappropriate for the main stream then let it be. I guess you would hear some
more complaints as there will be more ports on embedded platforms.
TL>
TL> regards, tom lane
TL>
--
Thanks,
Denis.
---(end of broadcas
On Mon, 20 Jan 2003, Tom Lane wrote:
TL> [EMAIL PROTECTED] writes:
TL> > The following line:
TL> > SELECT 1875/1000.0
TL> > produces different results. In 7.2.3 it is:
TL> > ?column?
TL> > -
TL> >1.875
TL>
TL> > while in 7.3.1 it is:
TL> > ?column?
TL> > ---
> + "PQconnectPoll() -- getsockopt() failed: "
> +"errno=%i\n",
> +WSAGetLastError());
> + connectFailureMessage(conn, "PQconnectPoll()", OptResult);
> + goto error_return;
> + }
> + #endif
>
> /*
2000-12-22 00:00:00+06
2000-12-25 00:00:00+06
2000-12-25 00:00:00+06
2000-12-25 00:00:00+06
2000-12-26 00:00:00+06
2000-12-27 00:00:00+06
2000-12-27 00:00:00+06
2000-12-27 00:00:00+06
2000-12-27 00:00:00+06
2000-12-27 00:00:00+06
2000-12-28 00:00:00+06
2000-12-29 00:00:00+06
2000-12-29 00:00:00+06
(45 rows)
Denis Osadchy
Russia, Novosibirsk
pgsql [31] $
configuration options were:
./configure \
--with-tcl \
--prefix=/usr/local/pgsql \
--with-template=openbsd \
--with-includes=/usr/local/include \
--with-libraries=/usr/local/lib \
--with-tkconfig=/usr/local/lib/tk8.0
Thanks!
--
Denis A. Do
; > Removing /usr/local/pgsql/data.
> > Removing temp file /tmp/initdb.32548.
>
> I faced with exactly the same trouble since PostgreSQL 6.4.
>
> Sincerely yours,
>
> Denis N. Stepanov.
> BINP SB RAS, Novosibirsk, Russia.
t; Removing /usr/local/pgsql/data.
> Removing temp file /tmp/initdb.32548.
I faced with exactly the same trouble since PostgreSQL 6.4.
Sincerely yours,
Denis N. Stepanov.
BINP SB RAS, Novosibirsk, Russia.
35 matches
Mail list logo
