The following bug has been logged on the website:
Bug reference: 7494
Logged by: Valentine Gogichashvili
Email address: val...@gmail.com
PostgreSQL version: 9.0.7
Operating system: Linux version 2.6.32-5-amd64 (Debian 2.6.32-41)
Description:
We are experiencing strang
The following bug has been logged on the website:
Bug reference: 6661
Logged by: Valentine Gogichashvili
Email address: val...@gmail.com
PostgreSQL version: 9.0.7
Operating system: Linux version 2.6.32-5-amd64 (Debian 2.6.32-41sque
Description:
Hello,
today when tryi
The following bug has been logged on the website:
Bug reference: 6375
Logged by: Valentine Gogichashvili
Email address: val...@gmail.com
PostgreSQL version: 9.1.1
Operating system: Debian 4.4.5-8
Description:
Hello,
default tsearch parser does not recognize all vali
> This process seems almost entirely unrelated to the documented way of
> doing it; I'm not surprised that you end up with some files not in sync.
> Please see pg_start_backup and friends.
>
> regards, tom lane
>
Hallo Tom,
It was done as documented in
http://www.postgre
On Jul 27, 5:02 pm, val...@gmail.com ("Valentine Gogichashvili")
wrote:
> The following bug has been logged online:
>
> Bug reference: 5574
> Logged by: Valentine Gogichashvili
> Email address: val...@gmail.com
> PostgreSQL version: 9.0beta3
> Operating system: RedHat Linux (2.
On May 19, 8:41 pm, m...@joeconway.com (Joseph Conway) wrote:
> Magnus Hagander wrote:
> > On Wed, May 19, 2010 at 5:10 AM, Valentine Gogichashvili
> > wrote:
> >> The following bug has been logged online:
>
> >> Bug reference: 5465
> >> Logged by: Valentine Gogichashvili
> >> Email
Oh, found an type in the subject. Transaction, not Translation.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On May 21, 3:04 am, alexei_nova...@yahoo.com ("Alexei") wrote:
> The following bug has been logged online:
>
> Bug reference: 4819
> Logged by: Alexei
> Email address: alexei_nova...@yahoo.com
> PostgreSQL version: 8.3.7
> Operating system: Open SuSE 11.1 AMD Athlon 64 X2
> Des
On Aug 6, 4:48 pm, [EMAIL PROTECTED] ("paull") wrote:
> The following bug has been logged online:
>
> Bug reference: 4342
> Logged by: paull
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2? not sure
> Operating system: ubuntu
> Description: upper, lower, init
On Aug 6, 5:06 pm, [EMAIL PROTECTED] ("paull") wrote:
> The following bug has been logged online:
>
> Bug reference: 4343
> Logged by: paull
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2? not sure
> Operating system: ubuntu
> Description: upper, lower, init
On Jul 28, 8:27 am, [EMAIL PROTECTED] ("andrew victoria") wrote:
> The following bug has been logged online:
>
> Bug reference: 4328
> Logged by: andrew victoria
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3.1
> Operating system: fedora core 9
> Description:
On Jul 25, 10:17 am, [EMAIL PROTECTED] (Zdenek Kotala) wrote:
> Valentine Gogichashvili napsal(a):
>
> > Hi,
>
> Hi
>
> > I understand, that it is more a feature, but it does not help me anyways...
>
> > On the UNICODE databases lower and upper functions are using system locale
> > settings (that c
I checked for de_DE.utf8 (created a test database with initdb) and
lower/upper is working correctly there on both 8.2 and 8.3 in
different languages
On Jul 22, 11:26 am, valgog <[EMAIL PROTECTED]> wrote:
> On Jul 21, 4:32 pm, [EMAIL PROTECTED] (Alvaro Herrera) wrote:
>
>
On Jul 22, 11:53 am, [EMAIL PROTECTED] (Peter Eisentraut) wrote:
> Am Tuesday, 22. July 2008 schrieb valgog:
>
> > Why Postgres allows creating UNICODE database with the locale, that
> > can possibly corrupt my data?
>
> It doesn't allow it, as of 8.3. In 8.2 it does
On Jul 21, 4:32 pm, [EMAIL PROTECTED] (Alvaro Herrera) wrote:
> Valentine Gogichashvili escribió:
>
> > On 8.2.3 database with LC_CTYPE set to en_EN, lower() function is actually
> > corrupting UTF8 data, lowering UTF8 control bytes... I did have a chance to
> > check if how it works on the 8.3 as
On Jul 21, 4:32 pm, [EMAIL PROTECTED] (Alvaro Herrera) wrote:
> Valentine Gogichashvili escribió:
>
> > On 8.2.3 database with LC_CTYPE set to en_EN, lower() function is actually
> > corrupting UTF8 data, lowering UTF8 control bytes... I did have a chance to
> > check if how it works on the 8.3 as
On Apr 25, 11:38 pm, [EMAIL PROTECTED] ("Kevin Grittner")
wrote:
> >>> On Fri, Apr 25, 2008 at 11:59 AM, in message
>
> <[EMAIL PROTECTED]>,
> valgog
>
>
>
>
>
> <[EMAIL PROTECTED]> wrote:
> > On Apr 24, 12:28 pm, [EMAIL PR
Ok, understood... that could not be so easy anyway :) I supposed that
it should be something, that lays in the JDBC specs...
Regards,
-- Valentine
On Apr 24, 12:28 pm, [EMAIL PROTECTED] (Kris Jurka) wrote:
> On Wed, 23 Apr 2008, valgog wrote:
> > Is it possible to impl
On Apr 22, 5:53 pm, [EMAIL PROTECTED] (Kris Jurka) wrote:
> On Tue, 22 Apr 2008, Amit Mujawar wrote:
>
> > The following bug has been logged online:
>
> > Bug reference: 4123
> > PostgreSQL version: 8.1
> > Description: Statement.setQueryTimeout does not work with Postgres
> > Java Driv
On Apr 22, 12:05 pm, [EMAIL PROTECTED] ("Amit Mujawar") wrote:
> The following bug has been logged online:
>
> Bug reference: 4123
> Logged by: Amit Mujawar
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: Windows XP
> Description: Statemen
Hi,
I am no sure if it is a bug at all, but according to the documented
features of UPDATE I would suppose it is.
UPDATE RETURNING clause cannot be used in SELECT * FROM ( query ) AS
query_alias statement.
For example:
update issues set issue_value = 'value to assign' where id in ( ) returning
21 matches
Mail list logo
