The following bug has been logged on the website:
Bug reference: 6342
Logged by: Andrea Grassi
Email address: andreagra...@sogeasoft.com
PostgreSQL version: 8.4.8
Operating system: SUSE SLES 10 SP4 64 BIT
Description:
Hi,
I have a big and strange problem. Sometimes,
Hi All, please help.
I Have PostgreSQL server 8.4.9 on Linux, database utf-8 and Client app on
Windows (VC++ and libpq.dll).
I need to use user account with non-ASCII and PQconnectdb() with
options="client_encoding=WIN1250" doesn't work.
SET CLIENT_ENCODING TO 'WIN1250' after PQconnectdb is too
Hi All, please help.
I Have PostgreSQL server 8.4.9 on Linux, database utf-8 and Client app on
Windows (VC++ and libpq.dll).
I need to use user account with non-ASCII and PQconnectdb() with
options="client_encoding=WIN1250" doesn't work.
SET CLIENT_ENCODING TO 'WIN1250' after PQconnectdb is too
Hello
this is not bug
you can try use a system variable PGCLIENTENCODING
bash-4.2$ PGCLIENTENCODING='latin2' psql postgres
psql (9.1.1)
Type "help" for help.
postgres=# show client_encoding ;
client_encoding
-
LATIN2
(1 row)
other way is connect with "only ascii" user name, c
Hi All, please help.
I Have PostgreSQL server 8.4.9 on Linux, database utf-8 and Client app on
Windows (VC++ and libpq.dll).
I need to use user account with non-ASCII and PQconnectdb() with
options="client_encoding=WIN1250" doesn't work.
SET CLIENT_ENCODING TO 'WIN1250' after PQconnectdb is too
On Thu, Dec 15, 2011 at 7:11 PM, Tom Lane wrote:
> maxim.bo...@gmail.com writes:
> > EXPLAIN analyze select *
> > from applicant_adv_subscription aas
> > where
> > aas.user_id in (5112699,7995496)
> > and exists (
> > SELECT * from resume
> > join resume_view_history using (resume_id)
> > where
>
The following bug has been logged on the website:
Bug reference: 6341
Logged by: Nelson Marques
Email address: nelson-m-marq...@ext.ptinovacao.pt
PostgreSQL version: 8.4.10
Operating system: Red Hat Enterprise Linux 5
Description:
Hi all,
Currently your binary distri
Thanx a lot for your promt respons :) You are absolutely right, its the
daylight saving that date and hour, I had it as an key in my GPS data and was
very confused!!!
Again - Thanx
/Hans-Henrik
On Dec 15, 2011, at 5:20 PM, Kevin Grittner wrote:
> wrote:
>
>> test to run: select to_timestamp('2
Hello Gabriel,
gabriel.marti...@greencore.co.cr [2011-12-15 15:02 +]:
> After the installation of postgresql (sudo apt-get install postgresql) isn't
> possible to start the service (sudo /etc/init.d/postgresql-8.4 start),
> simply doesn't happen anything and there is nothing in the logs.
I su
Excerpts from gabriel.martinez's message of jue dic 15 12:02:53 -0300 2011:
> The following bug has been logged on the website:
>
> Bug reference: 6337
> Logged by: Gabriel Martínez
> Email address: gabriel.marti...@greencore.co.cr
> PostgreSQL version: 8.4.9
> Operating system
wrote:
> test to run: select to_timestamp('2011,03,27,02,11,11',
> ',MM,DD,HH24,MI,SS')
>
> and the run: select to_timestamp('2011,03,27,03,11,11',
> ',MM,DD,HH24,MI,SS')
>
> It miscalculates 02 hour to 03 hour by some reason
I don't know what time zone you're in, or whether daylight
hfuxel...@gmail.com writes:
> test to run: select to_timestamp('2011,03,27,02,11,11',
> ',MM,DD,HH24,MI,SS')
> and the run: select to_timestamp('2011,03,27,03,11,11',
> ',MM,DD,HH24,MI,SS')
> It miscalculates 02 hour to 03 hour by some reason
If that date is a DST forward transition date
The following bug has been logged on the website:
Bug reference: 6340
Logged by: Hans-Henrik Fuxelius
Email address: hfuxel...@gmail.com
PostgreSQL version: 9.1.1
Operating system: Ubuntu 11.10
Description:
test to run: select to_timestamp('2011,03,27,02,11,11',
'
The following bug has been logged on the website:
Bug reference: 6339
Logged by: Gabriel Martínez
Email address: gabriel.marti...@greencore.co.cr
PostgreSQL version: 8.4.9
Operating system: Ubuntu 10.04.3 LTS
Description:
After the installation of postgresql (sudo apt
The following bug has been logged on the website:
Bug reference: 6337
Logged by: Gabriel Martínez
Email address: gabriel.marti...@greencore.co.cr
PostgreSQL version: 8.4.9
Operating system: Ubuntu 10.04.3 LTS
Description:
After the installation of postgresql (sudo apt
The following bug has been logged on the website:
Bug reference: 6338
Logged by: Gabriel Martínez
Email address: sopo...@greencore.co.cr
PostgreSQL version: 8.4.9
Operating system: Ubuntu 10.04.3 LTS
Description:
After the installation of postgresql (sudo apt-get inst
We have a similar issue with postgres 9.0.1
Any ideas?
I dint see any updates in the 9.1 release notes.. Has this issue been
addressed?
Regards,
Pratik Chirania
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-5578-postrgesql-database-crash-tp2259469p5077868.html
We have a similar issue with postgres 9.0.1
Any ideas?
I dint see any updates in the 9.1 release notes.. Has this issue been
addressed?
Regards,
Pratik Chirania
Hewlett-Packard
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-5578-postrgesql-database-crash-tp2259469p
maxim.bo...@gmail.com writes:
> EXPLAIN analyze select *
> from applicant_adv_subscription aas
> where
> aas.user_id in (5112699,7995496)
> and exists (
> SELECT * from resume
> join resume_view_history using (resume_id)
> where
> resume.user_id = aas.user_id
> );
I'm hoping to fix this type of ca
19 matches
Mail list logo
