The following bug has been logged online:
Bug reference: 4633
Logged by: Oleg
Email address: sero...@gmail.com
PostgreSQL version: PostgreSQL 8.3
Operating system: CentOS
Description:Bug in PL/PgSQL "SELECT .. INTO" statement parser
Details:
Here is
The following bug has been logged online:
Bug reference: 4673
Logged by: Oleg
Email address: sero...@gmail.com
PostgreSQL version: 8.3.6
Operating system: i686-redhat-linux-gnu
Description:pl/PgSQL: Bug, when updating changed composite types.
Details:
If you added
The following bug has been logged online:
Bug reference: 4688
Logged by: Oleg
Email address: sero...@gmail.com
PostgreSQL version: last stable
Operating system: CentOS
Description:Bug in cache.
Details:
Demo sql:
ROLLBACK;
BEGIN;
CREATE TABLE bug_composite_type
The following bug has been logged online:
Bug reference: 4710
Logged by: Oleg
Email address: sero...@gmail.com
PostgreSQL version: last stable
Operating system: CentOS
Description:Bug with sql functions, when using INSERT.. RETURNING ..
statment
Details:
Example
The following bug has been logged online:
Bug reference: 5314
Logged by: Oleg
Email address: sero...@gmail.com
PostgreSQL version: 8.3/8.4
Operating system: any
Description:Error in nested composite types in plpgsql.
Details:
Here is it reproduce code:
It works
The following bug has been logged online:
Bug reference: 5352
Logged by: Oleg
Email address: sero...@gmail.com
PostgreSQL version: any
Operating system: any
Description:Bug in PL/PgSQL "SELECT .. INTO" statement parser
Details:
CREATE TABLE test2 (
The following bug has been logged online:
Bug reference: 5353
Logged by: Oleg
Email address: sero...@gmail.com
PostgreSQL version: any
Operating system: any
Description:Bug in procedure When you modificate table
Details:
CREATE TYPE "buggy_enum_first&quo
The following bug has been logged online:
Bug reference: 5434
Logged by: Oleg
Email address: sacramento_...@mail.ru
PostgreSQL version: 8.4.3
Operating system: KUbuntu
Description:select from xpath_table gives wrong results
Details:
Here is a code:
create table
The following bug has been logged online:
Bug reference: 5852
Logged by: Oleg
Email address: sero...@gmail.com
PostgreSQL version: 8.3
Operating system: CentOS
Description:Function date_trunc is not IMMUTABLE
Details:
Please mark function date_trunc as IMMUTABLE
SQL BUG CODE:
BEGIN;
SELECT version(); -- "PostgreSQL 8.3.3 on i686-redhat-linux-gnu, compiled by
GCC gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-14)"
CREATE TYPE "buggy_enum_first" AS ENUM ( 'bug1', 'bug2', 'bug3' );
CREATE TABLE "bug_table" (
"id" BIGINT NOT NULL,
"buggy_enum_field" "buggy_enum_
Hello.
Seems there is an error when I try to use a table with one field - composite
type, when SELECT QUERY in FOR ... LOOP instruction returns empty result.
Here are steps to reproduce:
CREATE TYPE "t_type" AS (
"a" BIGINT
);
CREATE TABLE"t_table" (
"id" BIGINT NOT NULL,
"t" "t_type",
CONSTRAIN
Hello all SQL BUG CODE:
BEGIN;
SELECT version(); -- "PostgreSQL 8.3.3 on i686-redhat-linux-gnu, compiled by
GCC gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-14)"
CREATE TYPE "buggy_enum_first" AS ENUM ( 'bug1', 'bug2', 'bug3' );
CREATE TABLE "bug_table" (
"id" BIGINT NOT NULL,
"buggy_enum_field" "b
But if there are some records in t_table and we romove WHERE 1=0, we will
have
ERROR: wrong record type supplied in RETURN NEXT CONTEXT: PL/pgSQL function
"t_func" line 9 at RETURN NEXT
2008/9/1 Pavel Stehule <[EMAIL PROTECTED]>
> Hello
>
> 2008/9/1 Oleg Serov <[
Yes, you are right, with record type working correct;
Thanks
2008/9/2 Tom Lane <[EMAIL PROTECTED]>
> "Oleg Serov" <[EMAIL PROTECTED]> writes:
> > But if there are some records in t_table and we romove WHERE 1=0, we will
> > have
> > ERROR: wrong reco
SQL code:
ROLLBACK;
BEGIN;
CREATE TYPE "composite_type" AS (
"typename" VARCHAR
);
CREATE TABLE "buggy" (
"id" BIGINT NOT NULL,
"bug" "composite_type",
CONSTRAINT "buggy_pkey" PRIMARY KEY("id")
) WITH OIDS;
INSERT INTO buggy (id, bug) VALUES
(100196418052926086, NULL);
CRE
)::buggy;
IF tmp_old::text <> ROW(1, NULL)::buggy::text THEN
RAISE EXCEPTION '% <> %', tmp_old, ROW(1, NULL)::buggy;
END IF;
END;
$body$
LANGUAGE 'plpgsql' VOLATILE CALLED ON NULL INPUT SECURITY INVOKER;
WILL THROW A EXCEPTION:
ERROR: (1
I can't get hstore value by key. i have very interesting error
DEMO SQL CODE:
--
ROLLBACK;
BEGIN;
-- VERSION INFO
SELECT VERSION();
-- RESULT:
-- PostgreSQL 8.3.4 on i686-redhat-linux-gnu, compiled by GCC gcc
(GCC) 4.1.2 2
Ok, thanks... it is not a bug;
2008/10/27 hubert depesz lubaczewski <[EMAIL PROTECTED]>:
> On Mon, Oct 27, 2008 at 05:08:35PM +0300, Oleg Serov wrote:
>> I can't get hstore value by key. i have very interesting error
>
> the problem is that -> has very low priority,
SQL:
CREATE OR REPLACE FUNCTION "bug_with_triggers" () RETURNS trigger AS
$body$
BEGIN
PERFORM COALESCE(NEW.some_composite_field.field, TRUE);
END;
$body$
LANGUAGE 'plpgsql' VOLATILE CALLED ON NULL INPUT SECURITY INVOKER;
Error:
ERROR: NEW used in query that is not in a rule
QUERY: SEL
t;:
> Hello
>
> 2008/12/10 Oleg Serov <[EMAIL PROTECTED]>:
>> SQL:
>> CREATE TABLE second_type (
>>flag BOOLEAN
>> );
>> CREATE TABLE main_type (
>>subtype second_type
>> );
>> CREATE OR REPLACE FUNCTION "bug_in_tab
SQL:
CREATE TABLE second_type (
flag BOOLEAN
);
CREATE TABLE main_type (
subtype second_type
);
CREATE OR REPLACE FUNCTION "bug_in_tabletypes" () RETURNS pg_catalog.void AS
$body$
DECLARE
row_main_table main_type%rowtype;
BEGIN
row_main_table.subtype := NULL; -- all
The following bug has been logged online:
Bug reference: 4591
Logged by: Steblina OLeg
Email address: oldn...@ukrlink.net
PostgreSQL version: 8.1
Operating system: Windows XP pro sp2
Description:postgres.exe more than 150 processes runned
Details:
http
ved tag.
Comments?
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Regards,
Oleg
__
Sorry, but is not important, i forgot to remove original table name
"chunk_ad", but is not affected to the bug..
2009/1/21 Oleg Serov :
> Here is an example:
>
> CREATE TABLE test2 (
>id BIGINT,
>chunk_id BIGINT
> );
> CREATE TABLE test1 (
>
Here is an example:
CREATE TABLE test2 (
id BIGINT,
chunk_id BIGINT
);
CREATE TABLE test1 (
id BIGINT
);
CREATE OR REPLACE FUNCTION "bug" () RETURNS pg_catalog.void AS
$body$
DECLARE
row_test1 test1%rowtype;
row_test2 test2%rowtype;
BEGIN
SELECT test1, chunk_ad
Привет! Скажите пожалуйста адрес поддержки или помогите решить мою проблему. Я
не могу скачать PostgreSQL 8.0.3, версия не выше. Как узнать ссылку для
скачивания?
Hi! Tell me please mail support or help to solve my problem. I can not download
PostgreSQL 8.0.3, not version a
If i have tables with inherits, and the
n i adding a column in to the base table, the new column will be at
the on of column list in child table, but when i done dump->restore i
have surprise,
Column ordering was changed.
Some example:
CREATE TABLE test_base (
id INT
);
CREATE TABLE test_c
-- Dump/restore
INSERT INTO test_child_with_data
SELECT * FROM some_magic(); -- Error.
On Sun, Jul 5, 2009 at 4:48 AM, toruvinn wrote:
> On Sat, 04 Jul 2009 22:10:55 +0200, Oleg Serov wrote:
>>
>> INSERT INTO test_child_with_data
>> SELECT 1, 'test&#
UMERIC,
"ad_shop_select_views" NUMERIC,
"ad_emitted" NUMERIC,
"ad_redeemed" NUMERIC,
"client_payed" NUMERIC,
"mediapartner_charged" NUMERIC,
"ad_banner_views" NUMERIC,
"id" BIGINT NOT NULL,
"interval" "prt4_stat&q
;> This is not a bug, it's the intended behavior.
>
> I thought that was a bug, just one that was too hard to fix for the
> problems it caused. It might be more fixable if we get around to the
> work that was discussed earlier where we separate attnum into three
> different value
SQL:
CREATE TABLE test (id BIGINT, id2 BIGINT, id3 BIGINT, id4 BIGINT);
INSERT INTO test SELECT i, i, i, i FROM generate_series(0, 9) i;
EXPLAIN ANALYZE SELECT ((SELECT tmp::test FROM (SELECT * FROM test
LIMIT 1) tmp)::test).*;
WILL:
QUERY PLAN
Result (cost=0.11..0.12 rows=1 width=0) (actual time
The following bug has been logged online:
Bug reference: 5235
Logged by: Oleg Yurchenko
Email address: o...@fts.ee
PostgreSQL version: 8.4.1
Operating system: FreeBSD 8.0-RELEASE #0 Generic kernel i386
Description:Segmentation fault under high load through JDBC
code is following: select
instr(ad_parent_tree(?,?),'|'||?||'|') AS isItsOwnChild from dual;
Best regards,
Oleg.
Tom Lane wrote:
"Oleg Yurchenko" writes:
Program terminated with signal 11, Segmentation fault.
#0 0x0839380b in MemoryContextAllocZeroAligned (con
Both files are there.
Oleg.
Robert Haas wrote:
2009/12/8 Oleg Jurtšenko :
This the end of core dump. It is 8.3M bzip-ed. I can provide it on the
request.
I think maybe the beginning would be more useful than the end.
...Robert
--
Sent via pgsql-bugs mailing list (pgsql-bugs
Once more:
http://www.fts.ee/pgsqldebug.tgz
- with loging enabled
http://www.ftse.ee/pg_core.tar.bzip2
- full core dump
Robert Haas wrote:
2009/12/8 Oleg Jurtšenko :
Both files are there.
Both files are where? I don't see an attachment or a link.
...Robert
You are right, it crushes on following statement: "select
instr(ad_parent_tree(?,?),'|'||?||'|') AS isItsOwnChild from dual;"
max_stack_depth is commented out, I think it has the default value:
#max_stack_depth = 2MB
I'm attaching related functions.
Oleg
this function makes segmentation
fault also on FreeBSD 7.2 with Postgresql-8.3.7.
Consequentially, both Postgresql-8.3.7 and Postresql-8.4.1 are affected.
Oleg.
Tom Lane wrote:
Robert Haas writes:
2009/12/8 Oleg Jurtšenko :
You are right, it crushes on following statement: "se
Functions are attached
Oleg
Andrew Gierth wrote:
"Oleg" == Oleg Jurtšenko writes:
Oleg> I tried to execute "select instr(ad_parent_tree(?,?),'|'||'?'||'|') AS
Oleg> isItsOwnChild from dual;" query with psql terminal and
k 25 seconds to get
a result.
Regards, Oleg
Tom Lane wrote:
Andrew Gierth writes:
Still, even though the code is preposterous, the result shouldn't be a
segfault. I wasn't able to reproduce one myself (using 8.3.7 on
freebsd 7.2) however.
Yeah, for me it also recurses
Somebody will fix this bug or not?
On Thu, Feb 4, 2010 at 7:13 PM, Oleg wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5314
> Logged by: Oleg
> Email address: sero...@gmail.com
> PostgreSQL version: 8.3/8.4
> Operating sys
When it could be fixed?
On Thu, Feb 11, 2010 at 9:58 PM, Tom Lane wrote:
> Robert Haas writes:
>> 2010/2/10 Oleg Serov :
>>> Somebody will fix this bug or not?
>
>> I'm not sure whether this is a bug.
>
> Yeah, I think it is. The problem is that exec_m
Thanks!, when it will be released on 8.3.X?
On Wed, Feb 24, 2010 at 6:17 PM, Tom Lane wrote:
> Oleg Serov writes:
> > When it could be fixed?
>
> Oh, it is fixed, but I forgot to reply to this thread about it.
> Sorry about that.
>
>rega
Hello!? anybody will fix this bug? Hey!
On Mon, Feb 23, 2009 at 5:11 PM, Oleg wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4673
> Logged by: Oleg
> Email address: sero...@gmail.com
> PostgreSQL version: 8.3.6
> Operating sys
Hey, anybody will answer here?
2008/7/4 Oleg Serov
> SQL BUG CODE:
> BEGIN;
> SELECT version(); -- "PostgreSQL 8.3.3 on i686-redhat-linux-gnu, compiled
> by GCC gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-14)"
> CREATE TYPE "buggy_enum_first" AS ENUM ( 'b
Up!, Anybody will answer on this bugreport?
On Fri, Sep 26, 2008 at 2:57 PM, Oleg Serov wrote:
> Sorry, bug is not in triggers, it is in PL/PGSQL var assign mechanism
> here it is an example:
> ROLLBACK;
> BEGIN;
>
> CREATE TYPE "composite_type" AS (
>
Up. Anybody will answer on this bug report?
2009/1/21 Oleg Serov
> Sorry, but is not important, i forgot to remove original table name
> "chunk_ad", but is not affected to the bug..
>
> 2009/1/21 Oleg Serov :
> > Here is an example:
> >
> > C
Up! Anybody will answer about the patch?
On Mon, Jul 6, 2009 at 11:20 AM, Oleg Serov wrote:
> How about adding this patch to postgresql it will slove the problem?
>
> On Sun, Jul 5, 2009 at 8:10 PM, Greg Stark wrote:
> > On Sun, Jul 5, 2009 at 4:28 PM, Tom Lane wrote:
> &
So there are no simple way to do it right, and it will be not fixed? Will
this bug appear in todo list?
On Fri, Feb 26, 2010 at 6:13 PM, Greg Stark wrote:
> 2010/2/26 Oleg Serov :
> > Up! Anybody will answer about the patch?
>
> The patch causes the inheritance history to
On Fri, Feb 26, 2010 at 9:29 PM, Tom Lane wrote:
> Oleg Serov writes:
> > So there are no simple way to do it right, and it will be not fixed? Will
> > this bug appear in todo list?
>
> It's not a bug, it's just what happens when you make the parent and
>
It i
I'm think you should add some abstract-layer for handling column ordering
not as they stored at disk. It is possible?
On Fri, Feb 26, 2010 at 10:32 PM, Alvaro Herrera wrote:
> Tom Lane escribió:
> > Oleg Serov writes:
> > > So there are no simple way to do it right, a
Submitted as #*5352 bug.*
2010/2/26 Oleg Serov
> Up. Anybody will answer on this bug report?
>
>
> 2009/1/21 Oleg Serov
>
>> Sorry, but is not important, i forgot to remove original table name
>> "chunk_ad", but is not affected to the bug..
>>
>&g
submitted as #5353
2010/2/26 Oleg Serov
> Hey, anybody will answer here?
>
> 2008/7/4 Oleg Serov
>
> SQL BUG CODE:
>> BEGIN;
>> SELECT version(); -- "PostgreSQL 8.3.3 on i686-redhat-linux-gnu, compiled
>> by GCC gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-14)
; NEW::TEXT THEN
> RAISE NOTICE 'var is not equals NEW';
> END IF;
>
> RETURN NEW;
> END;
> $body$
> LANGUAGE 'plpgsql';
>
> CREATE TRIGGER "t_bug" BEFORE INSERT
> ON type_row FOR EACH ROW
> EXECUTE PROCEDURE "
I'm asking to fix this =)
On Wed, Mar 3, 2010 at 9:53 PM, Robert Haas wrote:
> 2010/3/3 Oleg Serov :
> >
> >
> > 2010/3/1 Robert Haas
> >>
> >> It's not obvious whether this is the same as one of the various other
> >> problems you
uld
> easily happen due to intermediate conversions of datatypes
>
> For example: I wouldn't expect timestamp::date::text to equal
> timestamp::text. Textual representations are not necessarily
> consistent.
>
> I guess a better question for Oleg might be:
>
> "
ase note that first query shows WRONG result and second one is OK.
Regards.
Oleg.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
DE.ISO-8859-1). Watch the results - is your
locale ok?
If you are sure your locale is Ok, but still unsatisfied with locale
test - send your patches to me, please.
Oleg.
Oleg Broytmannhttp://members.xoom.com/phd2.1/[EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
POSTGRESQL BUG REPORT TEMPLATE
Your name : Oleg Broytmann
Your email address : [EMAIL
On Tue, 11 Apr 2000, Tom Lane wrote:
> Oleg Broytmann <[EMAIL PROTECTED]> writes:
> > gcc -O2 -I../../backend -I../../include -I../../interfaces/libpq -fPIC -c
>pgconnection.cc
> > In file included from pgconnection.cc:18:
> > pgconnection.h:76: syntax error b
CXX_STRING_HEADER correctly (no).
Yes, set to undef... and didn't compile libpq++. I think I need
./configure --disable-cxx and skip libpq++ at all...
Oleg.
Oleg Broytmannhttp://members.xoom.com/phd2.1/[EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
>From my /etc/rc.d/rc.local:
# increase RCVBUF to optimize proxy<->backend
echo 131072 > /proc/sys/net/core/rmem_max
# increase maximum opened files
echo 8192 > /proc/sys/fs/file-max
# increase shared memory
echo "1" > /proc/sys/kernel/shmmax
Regard
ea and should be removed.
I don't recall having seen a response from Oleg or Teodor, and would
like their input before making a final decision --- but at the moment
I think we should take that out.
Oleg or Teodor, I need a comment on this.
We agree with Tom in this case and we'll remov
The following bug has been logged online:
Bug reference: 3305
Logged by: Belykh Oleg
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: MAC OS X
Description:multiple Operator classes
Details:
Index scan use only default operator class anyway
The following bug has been logged online:
Bug reference: 3865
Logged by: Oleg Kharin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.6
Operating system: CentOS 5.1 x86 64-bit
Description:ERROR: failed to build any 8-way joins
Details:
After PostgreSQL
> 8.2 patch is here, if you need it now:
> http://archives.postgresql.org/pgsql-committers/2008-01/msg00164.php
Thanks. I have applied this patch and everything works fine.
Regards,
Oleg
---(end of broadcast)---
TIP 2: Don't &#
Hello, help me please,
I don't know how, but i got 2 postgres users.
How can I delete the first one
thx alot for your answers.
///
select passwd,ctid,
Achilleus,
we have regprocedure_7.4.patch.gz
(http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/)
Oleg
On Fri, 25 Jun 2004, Achilleus Mantzios wrote:
>
> Hi, i noticed a failure when i pg_dump/reload a database with tsearch2.sql
> installed.
>
> I get ERR
The following bug has been logged online:
Bug reference: 2290
Logged by: Oleg Mamontov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.x/8.1.x
Operating system: FreeBSD 4.x,5.x,6.x
Description:Incorrect sequence increment after backup/restore
Details:
If
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
The following bug has been logged online:
Bug reference: 2345
Logged by: Kashin Oleg
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: FreeBSD
Description:odbc driver doesn't work
Details:
Hello!
I've the trouble. I'd ins
dash.
In general though, there are always going to be cases where prefix
match doesn't work because of dictionary transformations ...
I'd index 'after dictionary transformations' lexemes as well as an
original to let prefix march always work.
regard
71 matches
Mail list logo
