FAQ
nameOleg-Serov
seenFeb 8, 2015
sinceJul 4, 2008
57
posts
4
groups
1
badge

4 groups

pgsql-bugs@postgresql.org (43 posts) pgsql-hackers@postgresql.org (8 posts) pgsql-general@postgresql.org (4 posts) php-internals@php.net (2 posts)

57 posts

Archive for php-internals@php.net Feb 2015 Re: Idea of optimizing php !empty(...) expression.
Archive for php-internals@php.net Feb 2015 Idea of optimizing php !empty(...) expression.
Archive for pgsql-general@postgresql.org Dec 2011 Re: Postgresql + corrupted disk = data loss. (Need help for database recover)
Archive for pgsql-general@postgresql.org Dec 2011 Re: Postgresql + corrupted disk = data loss. (Need help for database recover)
Archive for pgsql-general@postgresql.org Dec 2011 Re: Postgresql + corrupted disk = data loss. (Need help for database recover)
Archive for pgsql-general@postgresql.org Dec 2011 Postgresql + corrupted disk = data loss. (Need help for database recover)
Archive for pgsql-bugs@postgresql.org Jan 2011 BUG #5852: Function date_trunc is not IMMUTABLE
Archive for pgsql-bugs@postgresql.org Mar 2010 Re: Bug in triggers
Archive for pgsql-bugs@postgresql.org Mar 2010 Re: Bug in triggers
Archive for pgsql-bugs@postgresql.org Mar 2010 Re: Bug in triggers
Archive for pgsql-bugs@postgresql.org Mar 2010 Re: Bug in procedure When you modificate table
Archive for pgsql-bugs@postgresql.org Mar 2010 BUG #5353: Bug in procedure When you modificate table
Archive for pgsql-bugs@postgresql.org Mar 2010 Re: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Archive for pgsql-bugs@postgresql.org Mar 2010 BUG #5352: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: Diffrent column ordering after dump/restore tables with INHERITS
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: Diffrent column ordering after dump/restore tables with INHERITS
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: Diffrent column ordering after dump/restore tables with INHERITS
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: Diffrent column ordering after dump/restore tables with INHERITS
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: Bug in triggers
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: Bug in procedure When you modificate table
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: BUG #4673: pl/PgSQL: Bug, when updating changed composite types.
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: BUG #5314: Error in nested composite types in plpgsql.
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: BUG #5314: Error in nested composite types in plpgsql.
Archive for pgsql-bugs@postgresql.org Feb 2010 Re: BUG #5314: Error in nested composite types in plpgsql.
Archive for pgsql-bugs@postgresql.org Feb 2010 BUG #5314: Error in nested composite types in plpgsql.
Archive for pgsql-bugs@postgresql.org Nov 2009 Crazy query plan.
Archive for pgsql-bugs@postgresql.org Jul 2009 Re: Diffrent column ordering after dump/restore tables with INHERITS
Archive for pgsql-bugs@postgresql.org Jul 2009 Re: Diffrent column ordering after dump/restore tables with INHERITS
Archive for pgsql-bugs@postgresql.org Jul 2009 Re: Diffrent column ordering after dump/restore tables with INHERITS
Archive for pgsql-bugs@postgresql.org Jul 2009 Diffrent column ordering after dump/restore tables with INHERITS
Archive for pgsql-bugs@postgresql.org Mar 2009 BUG #4710: Bug with sql functions, when using INSERT.. RETURNING .. statment
Archive for pgsql-bugs@postgresql.org Mar 2009 BUG #4688: Bug in cache.
Archive for pgsql-bugs@postgresql.org Feb 2009 BUG #4673: pl/PgSQL: Bug, when updating changed composite types.
Archive for pgsql-bugs@postgresql.org Jan 2009 BUG #4633: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Archive for pgsql-bugs@postgresql.org Jan 2009 Bug in PL/PgSQL "SELECT .. INTO" statement parser
Archive for pgsql-bugs@postgresql.org Jan 2009 Re: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Archive for pgsql-hackers@postgresql.org Dec 2008 Future request: BgBouncer && "cache lookup failed for function": Auto recache function.
Archive for pgsql-bugs@postgresql.org Dec 2008 Re: plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE;
Archive for pgsql-bugs@postgresql.org Dec 2008 plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE;
Archive for pgsql-bugs@postgresql.org Dec 2008 Bug in plpgsql, when using NEW with composite field value.
Archive for pgsql-hackers@postgresql.org Nov 2008 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Archive for pgsql-hackers@postgresql.org Nov 2008 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Archive for pgsql-hackers@postgresql.org Nov 2008 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Archive for pgsql-hackers@postgresql.org Nov 2008 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Archive for pgsql-hackers@postgresql.org Nov 2008 Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Archive for pgsql-bugs@postgresql.org Oct 2008 Re: Bug in pl/pgsql with hstore OR bug in pl/pgsql IF (text field is boolean?)
Archive for pgsql-bugs@postgresql.org Oct 2008 Bug in pl/pgsql with hstore OR bug in pl/pgsql IF (text field is boolean?)
Archive for pgsql-hackers@postgresql.org Sep 2008 Fwd: Null row vs. row of nulls in plpgsql
Archive for pgsql-bugs@postgresql.org Sep 2008 Re: Bug in triggers