ion doing? Can you try to prepare a
simplified testcase, based on your knowledge of the app?
kind regards
Tomas
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
s with two sessions - one accessing
tables that are being dropped by the other one.
However the report mentions version 8.4.0. Tejas, the first thing you
should do is updating to the last 8.4.x version - i.e. 8.4.18. Now.
You're missing ~4 years of bugfixes (that might even fix the one you'
probably http://www.postgresql.org/support/professional_support/
regards
Tomas
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 14.9.2013 14:12, Tomas Vondra wrote:
> On 13.9.2013 18:07, stephane.wust...@lip6.fr wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 8451
>> Logged by: strexxx
>> Email address: stephane.wust...@lip6.fr
>>
ately from PostgreSQL. So pgsql-bugs is
not the right place to report the issue.
I reported the issue on github and I'll look into that today/tomorrow
https://github.com/tvondra/quantile/issues/4
so far it seems like a trivial bug in handling NULL values.
regards
Tomas
--
Sent via pgsql-
t; correct. Clearly seems like bug to me.
>
> No, that just means that we don't unload it from memory. Where the bits
> actually are, and whether the kernel has defenses against somebody
> modifying the executable, is not something you should be asking us.
> Talk to a kernel hacke
On 30.5.2012 22:35, Tom Lane wrote:
> Tomas Vondra writes:
>> whenever I run a C-function (part of an .so file) and the file is
>> overwritten, the connection crashes. Tested on 9.1.3 and 9.2-beta1.
>
> "Doctor, it hurts when I do this."
> "So don't
Hi,
whenever I run a C-function (part of an .so file) and the file is
overwritten, the connection crashes. Tested on 9.1.3 and 9.2-beta1.
It's 100% reproducible:
1) compile the attached file and copy the .so to pkglibdir
$ gcc -I/home/tomas/tmp/postgresql-9.1.2/src/include testc
oint Computer Conference, pp 380-389)
Not sure if those are the right papers, though.
Nevertheless, I find posting such requests on pgsql-bugs rather rude.
Tomas
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 18 Listopad 2011, 20:38, Tigran Mkrtchyan wrote:
> On Fri, Nov 18, 2011 at 6:52 PM, Tomas Vondra wrote:
>> On 18 Listopad 2011, 17:42, Tigran Mkrtchyan wrote:
>>>
>>> The following bug has been logged online:
>>>
>>> Bug reference: 6300
>&
st the questions to
the appropriate place, e.g. pgsql-general mailing list.
Tomas
>
> 1. why it logged with ERROR level as it clients application behavior.
>
> 2. is there a way to suppress it or could you add a way to suppress it.
>
>
> Thanks a lot,
>Tigran.
>
>
te the output of find /usr -name typemap?
Well, basically yes - I've searched and used the file that matched the
kernel. But the correct version is obviously in the /usr/lib/perl5/5.12.3
directory.
Aha! When I run configure like this
$ ./configure --with-perl --enable-nls=cs
then it wor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jun 26, 2011 at 05:27:47AM +, jose javier cabrera centeno wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6078
> Logged by: jose javier cabrera centeno
Ésto no es un bug de PostgreSQL. Por eso te sug
The following bug has been logged online:
Bug reference: 6074
Logged by: Tomas Enrique Cardozo Baudry
Email address: tomas.enrique.cardozo.bau...@gmail.com
PostgreSQL version: 8.4.4
Operating system: Centos 5.6
Description:postgresql service script
Details
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Mar 19, 2011 at 05:56:21AM +, Srikanth wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5936
[...]
> It was working till 4 days back and suddenly gave the below message.Please
> tell me what do do
This doesn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Mar 12, 2011 at 01:01:52PM +0530, Vishal wrote:
> Hello Robert,
>
> I checked my logs and found the following info -
>
> [1] Information (8196), test_db_connection: exception: The Report Server is
> unable to connect to the database. Database
t;> I know the xml2 module is deprecated and most of the functions was moved
>> into core (and behave correctly) but xslt_process function was not and
>> that's why xml2 module is used.
>>
>> Pavel Stehule already prepared a fix (see the attachment).
>
> I don&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jun 04, 2010 at 06:15:09PM -0400, Farid Zidan wrote:
[...]
> Let me reiterate the example, maybe it was too terse and you did not
> read it carefully,
No. I think most readers here have understood your problem perfectly.
Don't underestimate t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 02, 2010 at 10:18:24AM -0700, Chris Travers wrote:
> Suppose I live in Canada and I have two checking accounts for my
> business, one in CAD and one in USD. In essence I have to account for
> a floating balance of a foreign currency [...]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Mar 26, 2010 at 12:42:29PM +, sachin wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5392
> Logged by: sachin
> Email address: sachin.des...@gmail.com
> PostgreSQL version: PostgreSQL8.4.0
> Oper
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Mar 19, 2010 at 05:30:30AM +, Krishnamoorthy wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5380
> Logged by: Krishnamoorthy
> Email address: krishnac...@gmail.com
> PostgreSQL version: 8.0.3
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 23, 2010 at 01:42:30AM +, Jaime Mendieta wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5341
[...]
> cuando termino de instalar postgres 8.4.2 me sale un cuadro que dice
> "Problem running post-install
how to configure builders to launch
makefiles or what to do.
Any help will be apprecciated and write in-depth receipe, I am not a C/C++
developer (I am Java oriented).
Tomas
Robert Haas wrote:
>
> 2010/1/2 Tomas Studva :
>> Hi all gurus,
>>
>> I've encountered on my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jan 07, 2010 at 04:11:03AM +, Mike Landis wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5268
> Logged by: Mike Landis
> Email address: mlan...@pnmx.com
> PostgreSQL version: 8.4.1
> Operating s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jan 05, 2010 at 07:21:15PM +, robson wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5266
> Logged by: robson
> Email address: robsonott0...@gmail.com
> PostgreSQL version: 8
> Operating system:
It is not working also for dir "F:Programs\PostgreSQL".
Tomas
John R Pierce wrote:
>
> Tomas Studva wrote:
>> My case is WIN XP SP 2 and also when applied SP3. My system has only
>> one speciality as I know, that is I have windows installed on F
>> partiti
---
Now I am out of ideas, I can try to install some older version of
postgres, but i had some problems also with that (but it is not
important for this). I want to install this new version. Can u h
---
Now I am out of ideas, I can try to install some older version of
postgres, but i had some problems also with that (but it is not
important for this). I want to install this new version. Can u help me
please?
Sincerely Tomas Studva.
The files b
This is test message. Please ignore it.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Dec 29, 2009 at 11:03:31PM +, katherine cubero luna wrote:
[...]
> Cuando intento abrirlo o correr el servicio me da el siguiente error:
>
> "The ordinal 2821 could not be located in the dynamic link library
> LIBEAY32.dll"
Ésto probabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Nov 25, 2009 at 07:58:53AM +, savita wrote:
[...]
Hi, Savita --
> I have a file which has data of a table. Now I want to copy this data into
> postgres database.
this is most probably not a bug in PostgreSQL, so it doesn't make sense
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Nov 09, 2009 at 10:28:51PM +0100, Tim van Loon wrote:
>
> hello,
>
> I have problems with installing postgresql 8.3
t would be helpful if you provided some more details. As it is, you
leave it to our crystal ball to come up with things as "w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Sep 27, 2009 at 11:11:05PM -0500, Jaime Casanova wrote:
> On Sun, Sep 27, 2009 at 9:45 PM, Robert Haas wrote:
> >
> > (with apologies to anyone on this mailing list who ACTUALLY speaks
> > Spanish - it must have hurt to read that)
> >
>
> act
ested patch attached.
Regards, Tomas Psika
*** src/backend/commands/indexcmds.c.bak2009-09-19 11:56:57.0
+0200
--- src/backend/commands/indexcmds.c2009-09-19 12:09:17.0 +0200
***
*** 127,132
--- 127,133
Datum reloptions;
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 12, 2009 at 10:34:42PM +, jesus wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4807
> Logged by: jesus
> Email address: jesusmartinez0...@yahoo.es
> PostgreSQL version: 8.3
> Operating syste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 23, 2009 at 02:24:06PM +0100, artur ganc wrote:
> Hi,
> I am using phpPgAdmin administration tool for PostgreSQL and I would like to
> link it to my MS Access through standards such as OCDB. I want to be able to
> do all the SQL queries in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jan 26, 2009 at 03:16:37PM +0200, Heikki Linnakangas wrote:
[...]
>> Maybe
>>invalid connection limit %d (must be positive or -1, for "unlimited")
>
> Hmm, that sounds better, but it can also be 0.
Oops. "nonnegative", then. Creeping unrea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jan 26, 2009 at 02:26:05PM +0200, Heikki Linnakangas wrote:
> Dave Page wrote:
>> It's possible to set a per-database connection limit of < -1, which seems
>> bogus:
>
> Yeah. That's simple to fix, but I'm having trouble wordsmithing the error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 05, 2008 at 02:42:31PM +, Carlos wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4450
> Logged by: Carlos
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2
> Operating system: li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 30, 2008 at 01:28:05AM +, Hemantha wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4441
Hemantha,
no need to submit a bug, since this is most probably not a bug of
PostgreSQL. It's more a question to pos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 25, 2008 at 12:29:14PM +0200, [EMAIL PROTECTED] wrote:
> Dear Sur!
>
> My name is Peter Kovacs and I work at the National Szechenyi Library in
> Hunagry.
> The reason why im writing this letter is the follow:
> We are using Potgresql to st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Aug 23, 2008 at 10:07:58AM -0700, Eric P. Melbardis wrote:
> Hi
>
> Testing on my home system, looking good... will try on my office system
> Monday.
>
> Note:
> I am assuming that the uuid will mostly be used as a primary
> key on r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, May 31, 2008 at 10:51:35PM +0530, Shantanu wrote:
> Here is my real use case
>
> 1) We have nornal SELECT ...INTO calls in the procedure calls
> 2) However we landed ourselves with the following problem
> http://www.postgresql.org/docs/faqs.FA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, May 30, 2008 at 09:57:49PM +0530, Shantanu wrote:
> Hello experts,
>
>
> I am facing this error.
>
> mydb=> select version();
> version
>
>
out the false alarm, then.
This is from the git gateway as hosted here:
http://repo.or.cz/w/PostgreSQL.git
Owner: [EMAIL PROTECTED]
See the backlog for REL8_3_STABLE here:
http://repo.or.cz/w/PostgreSQL.git?a=shortlog;h=REL8_3_STABLE
As far as I can tell, aside from this problem the branch looks go
h REL8_3_STABLE:
configure
configure.in
doc/bug.template
src/include/pg_config.h.win32
src/interfaces/libpq/libpq.rc.in
src/port/win32ver.rc
Patch with a possible solution attached.
Best regards,
--
Tomas Szepe <[EMAIL PR
> Tomas Szepe <[EMAIL PROTECTED]> writes:
> >> Are you doing anything that would involve lots of updates in these
> >> catalogs --- maybe repeatedly renaming a column, or something like that?
>
> > Hmm, I typically use a pair of
> > "ALTER TABLE
ble DISABLE TRIGGER USER;"/
"ALTER TABLE table ENABLE TRIGGER USER;"
per almost every relation when loading a dump, other than that there's
only the initial db creation code (lots of plpgsql triggers and a couple
immutable functions) and then using temp tables for complicated q
here.
Well, I've never hacked on postgresql, so probably all I can do
is tar/rzip the whole data dir and put it up for download somewhere
(there is no sensitive data).
Thanks for your help,
--
Tomas Szepe <[EMAIL PROTECTED]>
postgresql.conf.gz
Description: application/gunzip
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
0x081cc4ba in exec_simple_query (
query_string=0x83f7c88 "vacuum full verbose analyze;") at postgres.c:963
#10 0x081cd23d in PostgresMain (argc=4, argv=0x83843b0, username=0x8384390
"kala")
at postgres.c:3530
#11 0x081a6785 in ServerLoop () at postmaster.c:3
ng "pg_tablespace" --- only table or database owner can vacuum
it
WARNING: skipping "pg_pltemplate" --- only table or database owner can vacuum
it
VACUUM
This is on x86 Linux. 8.2.6 does not exhibit the problem, or at least I haven't
run into it. What info do I need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jan 19, 2008 at 08:27:42AM +, John Cota wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3887
[...]
> Postgresql 8.2 on Fedora Core 8/VMware Server 1.04
> pgAdmin III on xp sp2
>
> I'm able to access it via
o the CVS logs, this was reverted in beta4 --- you sure you
> are testing the right beta?
Yes, I'm 100% positive I'm running 8.3beta4.
Thanks,
--
Tomas Szepe <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 1: if posting/readi
avior
in this respect?
Thanks,
--
Tomas Szepe <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message
The following bug has been logged online:
Bug reference: 3761
Logged by: Jose Tomas Eterovic
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4-r1
Operating system: Gentoo Linux
Description:Problems with to_char(timestamp) and milliseconds
Details:
When you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Nov 17, 2007 at 08:19:37AM +0800, Hussain Jawad-FXRM43 wrote:
> Hello Sir,
>
> I have installed postgresql DB on my Linux server.
>
> When I am trying to stop and start the DB, below error is reported in
> postgresql start up log file.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Oct 04, 2007 at 11:36:59PM +, Radim Kolar wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3654
> Logged by: Radim Kolar
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.5
> Operating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Aug 16, 2007 at 05:41:32PM -0500, Peter Koczan wrote:
> Hey, I found something that finally clears netstat's recv-q with async
> notifies. I don't quite understand what's going on, so any
> enlightenment would be greatly appreciated. As near as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 05, 2007 at 03:22:17PM -0500, Larry Rosenman wrote:
> try:
> DROP TABLE "MULTIPOLYGON";
>
> That should do it.
> (pardon the top post).
>
>
>
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 512-248-2683
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 19, 2007 at 09:53:26PM +, Jessica wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3034
> Logged by: Jessica
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2
> Operating system:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 19, 2007 at 08:27:32PM +, Luigi Tarenga wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3033
> Logged by: Luigi Tarenga
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Feb 17, 2007 at 10:36:11PM +, Skatepark Insaen wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3026
[...]
> Whats up with the new versions for postgres
I don't think this belongs here. It's up to Debian what
28.php
The patch didn't apply on top of vanilla 8.2.2, so I fetched the
current 8.2 CVS head - seems to work fine with our production db.
Thanks!
--
Tomas Szepe <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
EOF
CREATE FUNCTION
CREATE TABLE
CREATE INDEX
ERROR: attribute 1 has wrong type
DETAIL: Table has type character varying, but query expects character varying.
$
Just putting back the old 8.2.1 binaries is enough
(the problem disappears), no need to redump/reinitdb.
System: Linux 2.6.20, x86, gli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jan 25, 2007 at 09:33:14AM -0500, James Becerra wrote:
> Good Morning,
[...]
> What happened with my server, time ago the Postgres 8.1 had worked perfect,
> and 2 days ago it leaves.
> I used the command net stat a to see the ports and I c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Dec 02, 2006 at 06:44:23PM +, carmelo wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2805
> Logged by: carmelo
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.4.7
> Operating system:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Nov 22, 2006 at 10:56:16AM +, Raghava wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2776
> Logged by: Raghava
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operating system:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Nov 12, 2006 at 04:49:33PM +, Basil Evseenko wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2755
[...]
> # \d tables.cart
[no cart_id field]
> # \d tables.download
[cart_id field]
> # SELECT count(1) from t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Sep 13, 2006 at 04:34:16PM +, Fernando chamber hurtado wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2626
> Logged by: Fernando chamber hurtado
> Email address: [EMAIL PROTECTED]
> PostgreSQL v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Aug 16, 2006 at 09:03:08PM +, Dan Franklin wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2579
> Logged by: Dan Franklin
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operatin
On Tue, Aug 15, 2006 at 03:36:24PM +, niktto wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2577
> Logged by: niktto
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7-4-7
> Operating system: debian
> Description:Notice: Only varia
On Mon, Aug 07, 2006 at 09:40:59PM +, PFudd wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2565
> Logged by: PFudd
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operating system: Fedora Core 5
> Description:pg tool doesn
tpickers, especially those who are mostly silent
bystanders ;)
But I'd support the idea myself.
Thanks
-- tomas
signature.asc
Description: Digital signature
file is too large
It's not by chance on a FAT partition?
Regards
-- tomas
signature.asc
Description: Digital signature
On Tue, Jul 04, 2006 at 04:44:08PM +0200, Tomasz Ostrowski wrote:
> On Tue, 04 Jul 2006, Tom Lane wrote:
>
> > I think the real problem here is that regex matching is the wrong
> > tool for the job. Have you looked into a full-text index
> > (tsearch2)?
>
> So much to do with so little time...
On Sun, Jun 18, 2006 at 07:38:13PM +0530, vinayak Desai wrote:
> [EMAIL PROTECTED] ~]# createuser -a -d -e antonio
> createuser: could not connect to database template1: FATAL: user "root"
> does not exist
This is not a bug. It's just that root is not a known database user.
Typically there is an
On Tue, Apr 18, 2006 at 11:34:53PM +, Yusuf Siddiqui wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2400
> Logged by: Yusuf Siddiqui
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: Linux
> Description:'Ã'
On Mon, Mar 27, 2006 at 10:20:23AM +, JP Glutting wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2360
> Logged by: JP Glutting
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1 (8.0)
> Operating system: Windows XP SP2
> Description:
On Thu, Mar 16, 2006 at 11:03:59AM +0100, Tomas Klockar wrote:
[...]
> I would say that sorting V and W as the same character may work in a
> dictionary [...]
> Currently the sortingfunction in postgreSQL have disqualified itself
> from beeing used, and I do the sorting in java whic
On Thu, Mar 16, 2006 at 01:02:57PM +0100, Andreas Pflug wrote:
> Tomas Zerolo wrote:
[...]
> > export LANG=C pgadmin &
>
> This is a wrong advice.
> Mete, use the option dialog to select your favourite language. Don't
> touch the environment.
OK, I assume
ing used, and I do the sorting in java which treat them as
separate caracters.
This is my 5 cent,
/Tomas
On Tue, Mar 14, 2006 at 09:30:29AM +, Mete Akdogan wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2318
[...]
This is not a bug (and definitely not a PostgreSQL bug ;-)
> hi, i am a teaching assistant in www.deu.edu.tr, in one of our db courses,
> we are plannin
encoding of your client is not UTF-8. Try
some query like "SET client_encoding TO 'LATIN1'" to see if the problem
disappears. Better yet -- try to convince the client to use UTF-8
encoding.
HTH
-- tomas
signature.asc
Description: Digital signature
;s encoding (issue the SQL command ''SHOW
CLIENT_ENCODING'' to learn about that (or ''SET CLIENT_ENCODING'' to
change that)
- What is the locale of your client? (if it's on an unix-like system,
see above. Otherwise I have no idea).
Hope that helps
-- tomas
signature.asc
Description: Digital signature
On Tue, Nov 15, 2005 at 10:51:10PM -0700, Michael Fuhr wrote:
> On Wed, Nov 16, 2005 at 06:29:40AM +0100, Tomas Zerolo wrote:
> > AFAIK, serials are not guaranteed to produce sequential values; tehy
> > will produce unique values. That means that they can (and sometimes
> >
eans that they can (and sometimes
will) jump.
Think about it: how could a database achieve that when the rollback of
an ongoing transaction is always possible?
Regards
-- tomas
signature.asc
Description: Digital signature
On Fri, Nov 11, 2005 at 09:26:47PM +, Tom wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2037
> Logged by: Tom
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1-beta4
> Operating system: Windows XP
> Description:user function ca
On Sun, Oct 30, 2005 at 12:23:00PM -0800, Theodore Petrosky wrote:
> I don't know if this is a bug or my not understanding
> something.
[...]
> I get an error:
> ERROR: invalid UNICODE byte sequence detected near
> byte 0x8e
> CONTEXT: COPY ioinfo, line 177, column publication:
> "Elle D?cor"
> E
; BEGIN
> res:=0;
> raise notice 'select * from ptest1 order by $1 asc';
I don't think plpgsql expands variables within strings. You'll have
to concatenate yourself, like so:
raise notice 'select * from ptest1 order by ' || $1 || ' asc';
HTH
-- tomas
signature.asc
Description: Digital signature
screwed up. Or maybe not...
>
> my dump file was as1.out so I...
>
> psql < as1.out
The data went into the $(whoami) database per default.
--
Tomas Szepe <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 6: Have you sea
On Nov-04 2003, Tue, 09:24 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> Tomas Szepe <[EMAIL PROTECTED]> writes:
> > Martin, you can probably rule out the cs_CZ (LATIN2) locale as the cause
> > of your problems -- I've been using that one for years on many produc
cs_CZ (LATIN2) locale as the cause
of your problems -- I've been using that one for years on many production
postgres systems (often huge and constantly loaded) and have never observed
the problems you're describing.
--
Tomas Szepe <[EMAIL PROTECTED]>
---
On Oct-15 2003, Wed, 02:08 -0400
Nayib Kiuhan <[EMAIL PROTECTED]> wrote:
> "date" timestamp DEFAULT 'now'
I believe you should be using
"date" timestampt DEFAULT CURRENT_TIMESTAMP(0)
--
Tomas Szepe <[EMAIL PROTECTED]>
nly
increasing by ~100 MiB a day, which, by my calculations, is roughly
proportional to the frequency of data added. (There is still
some minor overhead all right, but it's far from serious.)
So again it's a big thank-you to the whole postgres development
group for yet a
pg_catalog.setval ('seq_wtmp', 3928, true);
pgsql7.4beta3$ pg_dump -a -t seq_wtmp db1
pg_dump: specified table "seq_wtmp" does not exist
seq_wtmp is a perfectly normal sequence.
Bye,
--
Tomas Szepe <[EMAIL PROTECTED]>
--
-
Limit (cost=5152.26..5152.31 rows=20 width=104)
InitPlan
-> Limit (cost=0.00..1.11 rows=1 width=8)
-> Index Scan Backward using stats_hr_start on stats_hr
(cost=0.00..12059890.93 rows=10847279 width=8)
-> Sort (cost=5152.26..5162.55 rows=
> [EMAIL PROTECTED]
>
> Tomas Szepe wrote:
> >>[EMAIL PROTECTED]
> >>
> >>
> >>>indexes:
> >>>stats_min_pkey primary key btree (ip, "start")
> >>>stats_min_start btree ("start")
> >>>stats_h
7.4 should be able to recycle index space
> in that situation, but 7.3 and before can't.
OK, I'll definitely try 7.4 once I'm confident with it.
Thanks for your time,
--
Tomas Szepe <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
.
> > Hmm, you seem to suggest that we might expect a change in this regard
> > as 7.4 ships. Is that right?
>
> 7.4 should improve matters.
Trouble is, I probably can't give it a try on the production machine
unless I'm sure it won't trash the data
ic tables are stats_min and stats_hr.
--
Tomas Szepe <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
1 - 100 of 121 matches
Mail list logo
