as possible.
All mailing lists on postgresql.org (incl. pgsql-bugs, pgsql-hackers)
are operated by community, with participants from various companies. If
you decide you need a commercial support, the best place to start is
probably http://www.postgresql.org/support/professional_support/
regards
Tomas
not familiar with Arch Linux but I
guess it might be /var/log/postgresql.log or something like that.
Is there anything relevant in the logs?
Can you explain what is the application doing? Can you try to prepare a
simplified testcase, based on your knowledge of the app?
kind regards
Tomas
--
Sent
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
PostgreSQL version: 9.1.9
Operating system
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-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
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
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 testcomp.c
On 30.5.2012 22:35, Tom Lane wrote:
Tomas Vondra t...@fuzzy.cz 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 do that.
What exactly would you expect
has defenses against somebody
modifying the executable, is not something you should be asking us.
Talk to a kernel hacker for your platform.
OK, thanks for the explanation.
I still think it's worth mentioning this issue in the docs ...
Tomas
--
Sent via pgsql-bugs mailing list (pgsql-bugs
of 'duplicate key value violates unique
constraint'. I have two questions:
If it's a question, then why have you submitted it as a bug? This is not a
bug, it's correct and expected behavior - please, repost the questions to
the appropriate place, e.g. pgsql-general mailing list.
Tomas
1. why
On 18 Listopad 2011, 20:38, Tigran Mkrtchyan wrote:
On Fri, Nov 18, 2011 at 6:52 PM, Tomas Vondra t...@fuzzy.cz wrote:
On 18 Listopad 2011, 17:42, Tigran Mkrtchyan wrote:
The following bug has been logged online:
Bug reference: 6300
Logged by: Tigran Mkrtchyan
Email address
-nls
without with-perl? Allowing that and getting not-fully-working tree is
not a good thing I guess ...
Tomas
--
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 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 sugiero
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't
-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
) 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't see a response to this email, but it looks like Tom did apply a fix.
Yes, AFAIK there's a relevant discussion in the pgsql-hackers list.
regards
Tomas
--
Sent via
-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,br
No. I think most readers here have understood your problem perfectly.
Don't underestimate
-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
Operating
-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 step.
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 tstu...@gmail.com:
Hi all gurus,
I've encountered on my computer this bug. I will try to describe all what
I
-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:
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
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 belonging to this database system will be owned by user Homer.
This user must also own the server process.
The database cluster will be initialized
with that (but it is not
important for this). I want to install this new version. Can u help me
please?
Sincerely Tomas Studva.
-
LOG FILE
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
partition.
I was installing on path F
-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
-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 what
-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 robertmh...@gmail.com wrote:
(with apologies to anyone on this mailing list who ACTUALLY speaks
Spanish - it must have hurt to read
, 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;
int16 *coloptions
-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 system:
-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 MS
-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 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 unreadability,
-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: linux
-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 post
-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 store
-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 records
-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
-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
: [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 good
(and it compiled, and it seems to work).
Best regards,
--
Tomas Szepe [EMAIL PROTECTED]
--
Sent via pgsql
:
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 PROTECTED]
commit
,
--
Tomas Szepe [EMAIL PROTECTED]
postgresql.conf.gz
Description: application/gunzip
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
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 table DISABLE TRIGGER USER;/
ALTER TABLE table ENABLE TRIGGER
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 to submit so that this can be tracked down?
Best regards,
--
Tomas Szepe [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6
. Please let me know if you need additional info.
Best regards,
--
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
-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 pgAdmin
,
--
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 can get through to the mailing list
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/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
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 system:
-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 I
-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 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
Operating
-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: Unix
-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
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
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, glibc 2.5, gcc 4.1.1.
Hope this helps,
--
Tomas
-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 can
-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: linux
-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: RHEL
-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
-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
-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
Operating
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 variable
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't
)();
+
pg_dlclose(file_scanner-handle);
free((char *) file_scanner);
/* prv does not change */
shouldn't that be PG_fini_t?
(yeah, those nitpickers, especially those who are mostly silent
bystanders ;)
But I'd support the idea myself.
Thanks
-- tomas
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...
For what
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 user
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:
he sorting in java which treat them as
separate caracters.
This is my 5 cent,
/Tomas
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 you *do* know, gven your mail address
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 planning to
' 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
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
the rollback of
an ongoing transaction is always possible?
Regards
-- 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
will) jump
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
ERROR:
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
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 searched our list archives?
http://archives.postgresql.org
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]
---(end of broadcast)---
TIP
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]
---(end of broadcast
.)
So again it's a big thank-you to the whole postgres development
group for yet another nice step forward, especially to you Tom
for the allow btree index compaction and empty page reuse
changeset.
Best regards,
--
Tomas Szepe [EMAIL PROTECTED]
---(end of broadcast
the bloat is coming from the fact that the interesting range of
start changes over time. 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
[EMAIL PROTECTED]
Tomas Szepe wrote:
[EMAIL PROTECTED]
indexes:
stats_min_pkey primary key btree (ip, start)
stats_min_start btree (start)
stats_hr_pkey primary key btree (ip, start)
stats_hr_start btree (start)
ip is of type inet in all tables.
start is of type timestamp without
--
SELECT pg_catalog.setval ('seq_wtmp', 3928, true);
cut
pgsql7.4beta3$ pg_dump -a -t seq_wtmp db1
pg_dump: specified table seq_wtmp does not exist
cut
seq_wtmp is a perfectly normal sequence.
Bye,
--
Tomas Szepe [EMAIL PROTECTED]
---(end of broadcast
db (the dump is ~150 MiB gzipped).
--
Tomas Szepe [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
[EMAIL PROTECTED]
On Fri, 26 Sep 2003, Tomas Szepe wrote:
[EMAIL PROTECTED]
Did you use -f on the vacuumdb? If not, it did a normal vacuum (which
isn't likely to help) not a full vacuum.
There are scenarios where VACUUM FULL is not an option because
of its resource
[EMAIL PROTECTED]
Tomas Szepe [EMAIL PROTECTED] writes:
We have a production database that happens to receive several
thousand row updates per minute. We VACUUM ANALYZE every four
hours with max_fsm_pages set to 210, and it's no use.
Have you spent any time determining exactly
[EMAIL PROTECTED]
Tomas Szepe [EMAIL PROTECTED] writes:
I'm afraid so. The weird thing is, we once tried running
VACUUM FULL followed by REINDEX and although the process
took ages to complete, it didn't seem to help either. :(
I'll post whatever debug data I'm asked for, just don't
. 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, and I don't know of a way to
reproduce the workload on a test setup. :(
Thanks,
--
Tomas Szepe [EMAIL PROTECTED]
---(end
[EMAIL PROTECTED]
The resolution of this bug is of critical importance to me, will
somebody help?
Postgres version? Platform?
Ouch, sorry. PostgreSQL 7.3.3 on x86 Linux.
--
Tomas Szepe [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3
the rest of it is okay, but ... :-(
Tom, you've saved the day again! (Thanks thanks thanks.)
(BTW, it seems the bug can't be triggered on Linux/sparc32).
--
Tomas Szepe [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: don't forget to increase your
, will
somebody help?
Thanks, T.
- Forwarded message from Tomas Szepe [EMAIL PROTECTED] -
Date: Thu, 10 Jul 2003 11:54:14 +0200
From: Tomas Szepe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: segfault at aset.c:539
Hi list,
I'm getting an ugly non-deterministic segfault in postmaster
[EMAIL PROTECTED]
Peter Childs [EMAIL PROTECTED] writes:
On Fri, 30 May 2003, Tomas Szepe wrote:
Trouble is, as the rows in the tables get deleted/inserted/updated
(the frequency being a couple thousand rows per minute), the database
is growing out of proportion in size
1 - 100 of 109 matches
Mail list logo
