It happens often enough and the episodes last long enough that grabbing
a handle dump while this is going on should be easily done.
Regarding the Win32 error code, backend/storage/file/fd.c calls
_commit().
http://msdn2.microsoft.com/en-us/library/17618685(VS.80).aspx It looks
like it is alread
Here's the evidence from this morning. I have to admit I'm not really
sure what to make of it though.
Pete
The fsync / Permission denied errors occurred on 2 of 3 active servers
for the 7 am CLUSTER cycle.
Server #1 (with fsync errors):
- Both old and new relfilenodes are still visible with a
I'm not sure that's the whole story. "Server #3" had backends with
handles to the old relfilenode. It didn't have any fsync errors and the
old relfilenode was apparently successfully deleted (or at least it
wasn't visible in the file system anymore). That's the part of the
morning's investigatio
Am Mittwoch, 19. April 2006 01:34 schrieb Yusuf Siddiqui:
> The character 'Ã' is rejected as an invalid UTF-8 character.
Please show the output of
$ psql -c 'show client_encoding'
$ locale
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---
This is probably somewhat superfluous, but we had another one these
incidents last night whose details confirm your explanation here.
[2006-04-21 00:22:19.500 ] 2452 LOG: could not rename file
"pg_xlog/0001011A004C" to
"pg_xlog/0001011A0071", continuing to try
the autovac
Sure.
I should note that we're moving to Linux for our production servers so
our interest in the Windows port is waning (at least for the time
being). In particular, the stuck WAL segment rename problem has
occasionally been rather a pain in the neck.
As long as we still have Windows test server
With the patch applied, I let an inhouse stress test run for several
hours and it completed without incident. I also ran two runs of pgbench
with 50 connections x 1000 transactions and one run of 50 connections x
5000 transactions. All completed successfully. (Test server is a dual
Xeon with Hyp
Test server has SP1. This bug has only bit us twice (and never in a
testing environment) so it's hard to say (from our experience).
The successful pgbench runs are definitely good to see though.
Pete
>>> "Magnus Hagander" <[EMAIL PROTECTED]> 05/02/06 10:14 am >>>
Great news. One question though
The following bug has been logged online:
Bug reference: 2440
Logged by: Peter Exner
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3 / 8.1.3
Operating system: SuSe Linux
Description:TEMP TABLES in Postgres 8.1.3
Details:
Hello,
there is a problem with
On tor, 2010-05-27 at 22:41 +0100, Thom Brown wrote:
> This probably isn't a legitimate bug, but as a precaution
>
> I'm running the following command against PostgreSQL 9.0 beta 1:
>
> psql -U postgres -d test -c "select tablename,
> pg_size_pretty(pg_table_size(tablename::regclass)) from pg
The following bug has been logged online:
Bug reference: 5520
Logged by: Peter Mengaziol
Email address: pmengaz...@electrainfo.com
PostgreSQL version: 8.4.4
Operating system: OS X 10.4.13
Description:PG unable to find java stored procs without input
parameters
The following bug has been logged online:
Bug reference: 5524
Logged by: Peter Gagarinov
Email address: pgagari...@alliedtesting.com
PostgreSQL version: 9.0 Beta 2
Operating system: Windows XP Professional SP2
Description:SQLSTATE exception thrown from exception
On fre, 2010-07-02 at 14:01 +0100, Mike Fowler wrote:
>
> The attached patch is a very small patch that changes parse_expr.c
> to
> not convert everything to xml. This now means that when passed
> malformed XML it will return false instead of throwing an exception.
> In my mind this acceptab
The following bug has been logged online:
Bug reference: 5537
Logged by: Peter Abrahamsen
Email address: rainh...@gmail.com
PostgreSQL version: 9.0beta2
Operating system: Darwin x86_64 (MacOS 10.6.4)
Description:Makefile.darwin broken
Details:
Makefile.darwin
On mån, 2010-07-12 at 19:08 +0200, Antonio Rivas Valle wrote:
> Hi
>
> I downloaded PostgreSQL-8.4.4 for Windows (french version) a few days
> ago. Starting psql, I got a warning related to a possible
> malfunction because of the page code of the console. Every
> character with acc
On tis, 2010-07-13 at 02:11 +, Rafael Almeida wrote:
> The following bug has been logged online:
>
> Bug reference: 5558
> Logged by: Rafael Almeida
> Email address: raf...@rafaeldeveloper.com
> PostgreSQL version: 9.0
> Operating system: Windows XP
> Description:P
On mån, 2010-07-19 at 13:32 +0100, Dave Page wrote:
> I'm working on setting up a new buildfarm member as we don't seem to
> have any active Solaris ones :-(
>
> cc -Xa -m64 -mt -mt -D_REENTRANT -D_THREAD_SAFE
> -D_POSIX_PTHREAD_SEMANTICS -KPIC -DFRONTEND -DUNSAFE_STAT_OK -I.
> -I../../../src/in
On mån, 2010-07-19 at 13:32 +0100, Dave Page wrote:
> I'm working on setting up a new buildfarm member as we don't seem to
> have any active Solaris ones :-(
>
> cc -Xa -m64 -mt -mt -D_REENTRANT -D_THREAD_SAFE
> -D_POSIX_PTHREAD_SEMANTICS -KPIC -DFRONTEND -DUNSAFE_STAT_OK -I.
> -I../../../src/in
On ons, 2010-08-04 at 18:19 -0400, Tom Lane wrote:
>
> This policy also implies that we are never going to allow default
> arguments for aggregates, or at least never have any built-in ones
> that use such a feature.
>
> By my count the following people had offered an opinion on making
> this cha
On tor, 2010-08-05 at 14:38 -0400, Tom Lane wrote:
> Huh? The functionality proposed for removal is only that of omitting
> an explicit delimiter argument for string_agg(). Since the default
> value (an empty string) doesn't seem to be the right thing all that
> often anyway, I'm not following wh
On tis, 2010-08-03 at 14:36 +, Dmtiriy Igrishin wrote:
> When 'configure' executed in a directory outside the source tree the
> documentation is not installs later nevertheless the "gmake
> install-docs" or
> "gmake install-world" (I tried to build with "gmake world" also) typed
> to
> install
On tor, 2010-08-26 at 14:06 -0400, Tom Lane wrote:
> Peter Eisentraut writes:
> > We could fix this in several ways. Either hardcode exceptions for the
> > 'html' directory in prep_buildtree, or only create directories that
> > contain a makefile, which could al
On ons, 2010-09-01 at 16:22 +0200, Fabien COELHO wrote:
> I'm suggesting uniqueness in the "information_schema", which can be
> provided independently by some tweaking in the view construction, I
> think, for instance by adding the oid of the constraint or maybe the
> table_name.
The view is defi
On tor, 2010-09-02 at 07:54 +0200, Fabien COELHO wrote:
> > We cannot change it.
>
> Yes we can! It, it is 100% postgresql:
>
> \d information_schema.referential_constraints
>View "information_schema.referential_constraints"
>...
> FROM pg_namespace ncon
> JOIN pg_constraint co
On fre, 2010-09-03 at 13:53 -0400, Tom Lane wrote:
> Alvaro Herrera writes:
> > Excerpts from Fabien COELHO's message of vie sep 03 13:39:19 -0400 2010:
> >> I tried to explained that I'm analyzing other people's schemas. I cannot
> >> ask all other people on the planet to rewrite their schemas,
The correct way to do what he wants to do is
configure PYTHON=/usr/local/bin/python3.1 ... other options ...
On lör, 2010-09-11 at 17:22 -0700, Josh Berkus wrote:
> I discussed this report with James Pye already, and he beleives it's a
> configure script bug which should be fixed before release
On mån, 2010-09-13 at 13:51 -0400, Tom Lane wrote:
> Peter Eisentraut writes:
> > The correct way to do what he wants to do is
> > configure PYTHON=/usr/local/bin/python3.1 ... other options ...
>
> Hm, maybe this isn't adequately documented? Or at least should be
&
On tis, 2010-09-14 at 12:34 -0400, Tom Lane wrote:
> Heikki Linnakangas writes:
> > On 14/09/10 17:08, thommy wrote:
> >> -[ RECORD 2 ]+---
> >> feature_id | B032
> >> feature_name | Extended dynamic SQL
> >> sub_feature_id | 01
> >> sub_feature_name |
> >>
On sön, 2010-09-19 at 09:41 +, saer...@hotmail.com wrote:
> The Sequence view in the information schema is incomplete. It does not
> return a Sequence's maximum_value, minimum_value or increment. Please
> complete the view.
This is known and documented:
http://www.postgresql.org/docs/8.4/stati
On mån, 2010-09-20 at 20:53 +0100, Graham Swallow wrote:
> The file is in the wrong directory (probably).
> How it got there - is beyond my pay grade.
> I can only tell you that it is fixed here, by moving it,
>
> I should have told you that the problem occurs when compiling
> src/backend/utils/ca
On sön, 2010-09-19 at 14:28 -0400, Tom Lane wrote:
> What about inventing a function to extract a sequence's parameters?
> Perhaps something like
>
> pg_sequence_parameter(seq regclass, colname text) returns
> bigint
>
> which would do an appropriate permissions check and then fetch the
>
On tor, 2010-09-23 at 08:36 +0200, Magnus Hagander wrote:
> I wonder if we want to have a default value for this rather than
> disabling it when it's not specified by configure. But is there any
> kind of reasonable default that's not going to be
> platform/distribution specific?
I would like for
On tor, 2010-09-23 at 16:45 +0100, Dave Page wrote:
> On Thu, Sep 23, 2010 at 3:19 PM, Samuel Rettore wrote:
> > Hi,
> >
> > I'm having problems installing the database, see:
> >
> > anfitrite:/opt# ./postgresql-9.0.0-1-linux.bin
> >
> > Error: Error running /tmp/postgresql_installer/getlocales :
On tor, 2010-09-23 at 23:56 +0100, Dave Page wrote:
> > Surely the error message can be polished, though?
>
> Well we don't know what errors we might get on unsupported platforms
> until we test them, and we certainly don't have the resources to test
> every unsupported platform. It's hard enough
On fre, 2010-09-24 at 09:01 +0100, Dave Page wrote:
> How else would you suggest we find out what may go wrong on an
> unsupported platform?
Well, some amount of robust and defensive programming can probably
create better error messages in even the most unknown environment.
Especially since the pr
On fre, 2010-09-24 at 11:38 +0100, Dave Page wrote:
> I didn't know that existed - thanks. Unfortunately the first box I
> tried it on didn't have it, but that's quite old and not a supported
> platform anyway. if it does exist on everything we support, then that
> could work.
It's tempting, but I
On fre, 2010-09-24 at 16:10 +0100, Dave Page wrote:
> The download page states exactly what distros we consider supported.
Sorry, I was actually looking at the Postgres Plus download page.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
On fre, 2010-09-24 at 09:50 +0200, Magnus Hagander wrote:
> > I'm thinking, libpq could really use a global (and, for that matter, a
> > per-user) configuration file, where you could set defaults for some of
> > the things that you currently have to use environment variables for,
> > e.g., sslmode.
The following bug has been logged online:
Bug reference: 5689
Logged by: Peter Ajamian
Email address: pe...@pajamian.dhs.org
PostgreSQL version: 8.4.4
Operating system: CentOS 5.5
Description:UPDATE locks index before table resulting in deadlock
Details:
I got this
On fre, 2010-10-08 at 16:13 -0700, Bryson Holland wrote:
> what other information do you need from me to make this useful?
Platform, version, command line
> configure: WARNING: uuid.h: present but cannot be compiled
> configure: WARNING: uuid.h: check for missing prerequisite headers?
> confi
ng the right typmod
> to
> I/O functions. This is a regression, and it's particularly annoying
> because the other three standard PLs get this case right. Peter?
Never thought of that, typmods have a tendency to get lost somehow. :-/
Fix looks good; also good to get rid of the us
On sön, 2010-11-28 at 07:56 -0500, Robert Haas wrote:
> I guess it's not a bug if we did it that way on purpose, but it seems
> like testing for actual group membership would be less surprising.
I agree this is pretty confusing and would consider changing it.
--
Sent via pgsql-bugs mailing list
On sön, 2010-12-05 at 00:25 +, Adrian Klaver wrote:
> Seems there was a change in behavior for plpythonu with regards to
> boolean fields from 8.4 to 9.0. Previously, setting a field inside a
> plpythonu function to "f" would work, now that returns a 't' in the
> database field. To get the 'f'
The following bug has been logged online:
Bug reference: 5794
Logged by: Peter Speck
Email address: sp...@vitality.dk
PostgreSQL version: 9.0.2
Operating system: Mac OS X Server 10.6.5
Description:'explain' fails, but executing sql is ok.
Details:
The fol
On mån, 2010-12-20 at 02:39 +, Leslie Satenstein wrote:
> The insert examples in section 2.4 do not function if a cut and paste
> from
> pdf to psql is done
>
> This is the problem
> INSERT INTO weather VALUES (’San Francisco’, 46, 50, 0.25,
> ’1994-11-27’);
> The fields city and date should
On tis, 2010-12-28 at 12:19 +, Mario Ohnewald wrote:
> However, during the make, postgres requires perl devel. Should this
> not be covered in the configure script?
No, it's not configure's job to do the job of make or the compiler.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql
On tis, 2010-12-28 at 15:29 -0800, John R Pierce wrote:
> I believe he's suggesting that configure should be confirming the
> availability and location of these prerequisites, just as it locates
> and validates the perl install and many other prerequisite tools.
Sure, but that's just extra code t
On tis, 2010-12-28 at 18:30 -0500, Gurjeet Singh wrote:
> What is the difference between this and how libreadline or zlib are checked
> by configure? I am referring to the configure error that pronpts us to use
> --without-readline.
Sure, it's inconsistent. It's just a matter of how much code you
CREATE TYPE zzz_enum AS ENUM ('A', 'B', 'C');
CREATE TABLE zzz_test1 (z zzz_enum);
SELECT * FROM zzz_test1 WHERE z = 'A';
That works. But:
CREATE DOMAIN zzz AS zzz_enum DEFAULT 'A';
CREATE TABLE zzz_test2 (z zzz);
SELECT * FROM zzz_test2 WHERE z = 'A';
ERROR: 42883: operator does not exist: zzz
On fre, 2011-01-21 at 17:31 +0100, Giacomo Petillo wrote:
> Hi,
> in the help of "pg_dumpall" pops up this error:
>
> Opzioni di connessione:
> -h, --host=NOMEHOST host server di database o directory socket
> -l, --database=NOMEDBpreimpostazione database alternativo
> *p, --port=POR
On sön, 2011-02-06 at 11:06 -0500, Tom Lane wrote:
> I don't know the state of affairs on FreeBSD for sure, but I do know
> that the UTF-8 locales are fairly broken on Mac OS X, which is a BSD
> derived platform too. It looks like nobody in BSD-land has bothered
> to put in the work to make multib
On ons, 2011-02-16 at 17:15 +, Khadtare, Sharad wrote:
> I want to configure Bidirectional replication in postgres 9 ( streaming ).
>
> any one knows solution for Bidirectional replication in postgres.
This is not a bug, and is hence inappropriate for this forum. But what
you are looking for
On ons, 2011-03-02 at 18:00 +0200, Heikki Linnakangas wrote:
> Hmm, regardless of what's causing this, I wonder if we should check
> that the locale works at CREATE COLLATION time, rather than fail when
> you try to use it. Ie. add a call to pg_newlocale_from_collation() at
> the end of DefineColla
On ons, 2011-03-02 at 21:59 +0200, Peter Eisentraut wrote:
> On ons, 2011-03-02 at 18:00 +0200, Heikki Linnakangas wrote:
> > Hmm, regardless of what's causing this, I wonder if we should check
> > that the locale works at CREATE COLLATION time, rather than fail when
> >
On tis, 2011-03-22 at 06:34 +, Vincent Chan wrote:
> when saving a bytes array,
> for example a bytes array which length is 2,
> but after saving,
> it's length will be change to 3.
> but in postgres 8.4, the array length is still 2.
Please show an actual example of what you are observing.
On Tue, 2011-04-19 at 12:52 +, Daniel Migowski wrote:
> I would love to give pg_dump an option to produce ordered output. This would
> make it much easier to create dump files that are comparable with a textual
> diff tools.
>
> The following orderings are required:
>
> * Dump objects ordered
On ons, 2011-05-11 at 14:58 -0400, Tom Lane wrote:
> Marc Cousin writes:
> > I've been starting to work on a 'what's new in 9.1' like i did last
> > year, and am faced with what I feel is a bug, while building a demo case
> > for collation.
>
> > Here it is:
>
> > SELECT * from (values ('llegar'
On lör, 2011-06-04 at 07:09 +, dinesh wrote:
> I have a table which is used during data uploads, a so-called staging table.
> This table has a fixed number of columns that [must] match the input CSV
> file. This CSV file is uploaded using COPY command. Following the COPY, a
> new column (meant
On ons, 2011-06-08 at 11:09 -0400, Tom Lane wrote:
> The omission of collection_type_identifier from the docs is clearly a
> doc bug. However, it looks to me like you've identified an error in the
> view definition, not only a doc bug. I think the values of the
> dtd_identifier and collection_typ
On ons, 2011-06-08 at 20:38 +0300, Peter Eisentraut wrote:
> On ons, 2011-06-08 at 11:09 -0400, Tom Lane wrote:
> > The omission of collection_type_identifier from the docs is clearly a
> > doc bug. However, it looks to me like you've identified an error in the
> > view
On ons, 2011-06-08 at 11:09 -0400, Tom Lane wrote:
> As far as I can tell from the spec, dtd_identifier
> ought to be the identifier of the element type, while
> collection_type_identifier should be a made-up identifier for the
> array type. That would make the sample query given in the docs
> cor
On tor, 2011-06-09 at 13:30 -0400, Bruce Momjian wrote:
> Column numbers in ORDER BY is ANSI syntax so I don't think calling
> them "legacy" is accurate. "limited functionality"?
It was in SQL 92, but removed in 99, so it's technically no longer part
of the standard.
--
Sent via pgsql-bugs mai
On fre, 2011-06-17 at 10:22 +0200, Bernd Helmle wrote:
>
> --On 17. Juni 2011 08:18:03 + Christoph Berg wrote:
>
> > In German locale, the follow statement causes vsnprintf() to segfault when
> > printing the hint:
> >
> > SELECT TO_DATE('30.12.2011', 'MMDD') AS datum;
> >
> > Fix tested
On fre, 2011-06-17 at 13:10 +0200, Christoph Berg wrote:
> Re: To pgsql-bugs@postgresql.org 2011-06-17
> <20110617091114.gc4...@msgid.df7cb.de>
> > Unfortunately that doesn't help in this case, as the bad string isn't
> > tagged as "#, c-format", but still gets used as such. This seems to be
> > t
On ons, 2011-08-03 at 21:02 +, Matthias Kurz wrote:
> SELECT
> a.companyname AS a_companyname,
> a.street,
> a.zip,
> a.city,
> a.country
> FROM
> myAddress a
> ORDER BY
> a_companyName COLLATE "C" DESC,
> a.street COLLATE "C" ASC,
> a.zip
On mån, 2011-04-25 at 11:03 -0400, Robert Haas wrote:
> >> but executing
> >>time make -j4 check
> >> fails (I don't see any obvious problem in the log file):
> >> [...]
> >> == creating temporary installation
> ==
> >>
> >> pg_regress: installation failed
> >> Examine
On tis, 2011-09-06 at 17:12 +0200, hubert depesz lubaczewski wrote:
> On Mon, Sep 05, 2011 at 02:27:23PM -0400, Tom Lane wrote:
> > It's not just the port, it's all the connection parameters ---
> > do_connect relies on the PGconn object to remember those, and in this
> > case there no longer is a
On tis, 2011-09-20 at 00:32 -0400, Tom Lane wrote:
> =?Big5?B?pHCoqA==?= writes:
> > Use ALTER TABLE item ALTER COLUMN title TYPE character varying(2000)
> > COLLATE pg_catalog."zh_TW.euctw";
> > but, SQL state: 42704 "UTF8" "pg_catalog.zh_TW.euctw" not found
>
> I hope that's not the exact p
On ons, 2011-09-28 at 22:42 -0400, Tom Lane wrote:
> "Pierre Ducroquet" writes:
> > [ the "hstore ? text" operator no longer matches an hstore GIST index ]
>
> Hmm ... this doesn't seem to be specific to either hstore or GIST; it's
> a collation problem. The index is marked as having no collatio
e "no relation entry for relid
1". Why is that?
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
On 29 September 2011 21:59, Merlin Moncure wrote:
> hm -- works for me (9.1.0)
It works for me on REL9_1_STABLE too, unsurprisingly, as I would think
it highly unlikely that such a glaring bug would slip into a stable
release.
--
Peter Geoghegan http://www.2ndQuadrant.com/
Postgre
On 29 September 2011 23:15, Tom Lane wrote:
> Peter Geoghegan writes:
>> I've built Postgres from master, and found that the following fairly
>> simple query breaks:
>
>> select count(*)
>> from
>> (
>> select
>> schemaname
>&g
I noticed this typo in a comment in the file nbtsort.c:
/*
* We need to log index creation in WAL iff WAL archiving/streaming is
* enabled UNLESS the index isn't WAL-logged anyway.
*/
I suggest an s/iff/if/
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development,
On ons, 2011-10-26 at 04:08 +, Shannon wrote:
> The following bug has been logged online:
>
> Bug reference: 6271
> Logged by: Shannon
> Email address: shan...@arc.net.au
> PostgreSQL version: 8.4.9
> Operating system: Gentoo Linux 64bit
> Description:psql -f repor
On tor, 2011-11-10 at 19:30 -0500, Tom Lane wrote:
> I think psql only pays attention to its locale when stdout is a tty.
> Now *why* it acts like that, I'll leave for Peter to defend.
We would have to review the original discussion about that. I can see
arguments for doing it that
INTERNAL_ERROR),
464:(errcode(ERRCODE_INTERNAL_ERROR),
526:(errcode(ERRCODE_INTERNAL_ERROR),
A new severity level is called for. In addition, if we had a new
severity level, the footprint wouldn't be too bad on all those legacy
elog() calls as compa
ot;severe error".
>
> +1
+1
On reflection, that's better than what I proposed.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On tor, 2011-11-24 at 11:14 -0500, Robert Haas wrote:
> So I would propose to steer clear of the word "internal", because the
> really scary errors typically are not internal to PostgreSQL at all.
> What I think we want to distinguish between is things that are
> PEBKAC/GIGO, and everything else.
On ons, 2011-11-23 at 12:07 +0100, Marco Bernasocchi wrote:
> Hi all, porting QGIS to android I ported libpq as well, I had to modify
> two files to successfully compile it without-readline. I attach the two
> needed minor patches. further informations can be found at android.qgis.org.
The Postg
inCE libpq port very successfully. I built it
from source too, as there were binary compatibility problems with some
of the ARM devices that had custom WinCE kernels (not uncommon - WinCE
is available under a "shared source" agreement), but not others that
didn't.
What'
On 11 December 2011 17:53, Cihan ŞENGÜL wrote:
> Hi
> Libpqwce are published. Gösterilemiyor.Bana reference to VB NET 2003. NET
> 2003, I can reference the DLL required for VB
I don't understand.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Sup
Line 834 of heapam.c has the following comment:
/*
* This is formatted so oddly so that the correspondence to the macro
* definition in access/heapam.h is maintained.
*/
In fact, that macro is defined in access/htup.h...should it be?
--
Peter Geoghegan http://www.2ndQuadrant.com
On 20 December 2011 18:11, Tom Lane wrote:
> Simon Riggs writes:
>> On Tue, Dec 20, 2011 at 5:50 PM, Peter Geoghegan
>> wrote:
>>> In fact, that macro is defined in access/htup.h...should it be?
>
>> IMHO comment is wrong, code is in the right place.
>
>
On fre, 2011-12-30 at 12:02 -0300, Alvaro Herrera wrote:
> Excerpts from thangalin's message of vie dic 30 11:30:47 -0300 2011:
> > The following bug has been logged on the website:
> >
> > Bug reference: 6368
> > Logged by: D J
> > Email address: thanga...@gmail.com
> > Postgre
ISTM that the following reference, at config.sgml line 1345, ought to
be adjusted due to the introduction of the new checkpointer process:
Setting this to zero disables
background writing (except for checkpoint activity).
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL
On 9 January 2012 18:47, Robert Haas wrote:
> On Sat, Dec 31, 2011 at 8:54 PM, Peter Geoghegan
> wrote:
>> ISTM that the following reference, at config.sgml line 1345, ought to
>> be adjusted due to the introduction of the new checkpointer process:
>>
>>
On 17 January 2012 01:37, Robert Haas wrote:
>> It's a fairly inconsequential bug, but it is worth fixing...
>
> Fixed.
Thanks.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing
On 20 January 2012 02:53, Robert Haas wrote:
> OK, done.
Thanks
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
h
I noticed the following in the auto_explain documentation:
"This can have extremely negative impact on performance."
Surely it should say:
"This can have an extremely negative impact on performance."
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Devel
here:
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chan
like an integrity constraint violation. I
continue to maintain that we should have a new severity level for this
sort of thing.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
ntain that we should have a new severity level for this
>> sort of thing.
>
> Huh? I don't follow you at all Peter.
I mean that we should change code like this:
elog(ERROR, "could not find plan for CTE \"%s\"", rte->ctename)
to this:
elog(INTERNAL_ERROR
the log
> to enable the DBA to figure out that the first error message is likely
> nothing more serious than an integrity constraint doing its bit to
> preserve data integrity, while the second is likely a sign of
> impending disaster.
Is it really that much of a problem to creat
On 29 January 2012 21:19, Peter Geoghegan wrote:
> Is it really that much of a problem to create a new severity level for
> this stuff?
I should probably have quoted this refinement, which was part of the
discussion that I originally quoted Robert from:
On 24 November 2011 16:55, Alvaro H
line with this
stuff. Should I continue to report trivialities like these as bugs? I
would think that in the case of documentation the answer is "yes", but
I can't help but feel slightly silly about reporting cases like this.
--
Peter Geoghegan http://www.2ndQuadrant.com/
Postg
On 29 January 2012 23:47, Josh Berkus wrote:
> This is *so* not a discussion to have on the pgsql-bugs list. Please
> take it to -hackers.
I suppose you're right, since the first discussion occurred there and
didn't really go anywhere.
--
Peter Geoghegan http://www
On fre, 2012-02-17 at 12:01 -0500, Tom Lane wrote:
> lenka.piy...@gmail.com writes:
> > when i restore a particular table using pg_restore (using option "-t") it
> > doesn't restore my primary key...
>
> This is not a bug. -t selects the table only, not associated indexes.
But from a user's per
On ons, 2012-02-22 at 22:37 +0400, Sergey Burladyan wrote:
> eshkin...@gmail.com writes:
>
> > The following bug has been logged on the website:
> >
> > Bug reference: 6480
> > Logged by: Sergey Burladyan
> > Email address: eshkin...@gmail.com
> > PostgreSQL version: 9.1.2
> > O
On lör, 2012-04-14 at 08:23 -0400, Robert Haas wrote:
> On Sat, Apr 14, 2012 at 3:27 AM, Pavel Stehule
> wrote:
> >> It has a lot of sense. Without it, it's very difficult to do logical
> >> replication on a table with no primary key.
> >>
> >> (Whether or not people should create such tables in
On tor, 2012-04-19 at 15:00 -0400, Tom Lane wrote:
> i+pgb...@avdd.tk writes:
> > A concurrent psql session will overwrite the history of the first. This
> > does not look good: a database tool causing me to lose my data!
>
> Works okay for me. I suspect you need to take this up with whoever
> p
701 - 800 of 900 matches
Mail list logo
