Sergey Konoplev escribió:
> On Tue, Jun 11, 2013 at 6:50 AM, Tom Lane wrote:
> > Sergey Konoplev writes:
> >> Just curious, what is the planned date for the next minor release, and
> >> BTW where is it possible to see the roadmap for minor releases?
> >
> > There is no planned date, and certainly
Alvaro Herrera wrote:
> AFAICS the problem here is that this test doesn't use MultiXactIds at
> all in 9.2, but it does in 9.3. I vaguely recall Noah tried to convince
> me to put in an optimization which would have avoided this issue; I will
> give that a thought. I don'
Oskari Saarenmaa wrote:
> 05.10.2013 01:31, Alvaro Herrera kirjoitti:
> > AFAICS the problem here is that this test doesn't use MultiXactIds at
> > all in 9.2, but it does in 9.3. I vaguely recall Noah tried to convince
> > me to put in an optimization which would have
Oskari Saarenmaa wrote:
> 05.10.2013 01:31, Alvaro Herrera kirjoitti:
> > AFAICS the problem here is that this test doesn't use MultiXactIds at
> > all in 9.2, but it does in 9.3. I vaguely recall Noah tried to convince
> > me to put in an optimization which would have
AFAICS the problem here is that this test doesn't use MultiXactIds at
all in 9.2, but it does in 9.3. I vaguely recall Noah tried to convince
me to put in an optimization which would have avoided this issue; I will
give that a thought. I don't think I will be able to get it done for
9.3.1 though.
I spent a lot of time looking at this issue. Your problem scenario can
be reduced to the following test case:
CREATE TABLE t (a INT);
INSERT INTO t VALUES (1);
The three sessions need to execute the following commands, in this
sequence:
-- Session 1
/* 1 */ BEGIN;
SELECT * FROM t FOR UPDATE;
-
ock" before the commit.
Yes, sounds pretty likely.
> And I'm thinking that also this commit is related to BUG#8470.
Yes, I replied to that thread because I suspect the same.
> If so, I hope Alvaro will find the solution for this problem.
I will take a look at this
o...@ohmu.fi wrote:
> The following code performs a lot slower on PostgreSQL 9.3.0 than on
> PostgreSQL 9.2.4:
>
> DROP TABLE IF EXISTS tmp;
> CREATE TABLE tmp (id BIGSERIAL, vals BIGINT[]);
> DO $$
> DECLARE
> r_id BIGINT;
> n BIGINT;
> BEGIN
> FOR n IN 1..1000 LOOP
> BEGIN
Andres Freund wrote:
> No need, found the bug. And I think can build a testcase myself.
>
> ExecReScanMergeAppend resets ms_initialized, but doesn't clear the
> binaryheap. Thus no new elements fit.
Um. Are we missing a binaryheap_clear() method?
--
Álvaro Herrerahttp://www.2n
george.strag...@gmail.com escribió:
> create type testPop as (
> FOOBAR int
> );
Your problem is that this identifier has been downcased. This works:
alvherre=# create type testPop as (
alvherre(# "FOOBAR" int);
CREATE TYPE
alvherre=# select * from json_populate_record(null::testPop, '{"F
Jesse Denardo escribió:
> Alvaro,
>
> I applied the patch and tried upgrading again, and everything seemed to
> work as expected. We are now up and running the beta!
Pushed, thanks.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Suppo
gerrit.ge...@hp.com wrote:
> template1=# CREATE DATABASE vergunnigen_sit;
> CREATE DATABASE
> template1=# GRANT ALL PRIVILEGES ON DATABASE vergunnigen_sit to postgres;
> GRANT
> template1=# \q
> -bash-4.1$ psql vergunningen_sit
> psql: FATAL: database "vergunningen_sit" does not exist
>
>
> Whe
Andres Freund escribió:
> On 2013-08-02 18:17:43 -0400, Alvaro Herrera wrote:
> > Alvaro Herrera escribió:
> >
> > > As it turns out, I have a patched slru.c that adds a new function to
> > > verify whether a page exists on disk. I created this for the commit
&g
Alvaro Herrera escribió:
> As it turns out, I have a patched slru.c that adds a new function to
> verify whether a page exists on disk. I created this for the commit
> timestamp module, for the BDR branch, but I think it's what we need
> here.
Here's a patch that should f
f...@libero.it wrote:
> problem:
> I have build from source posgresql (8.4) on a android table whith a minimal
> linux debian installed."configure" process and "make" (compiling source) and
> "make install": all are OK!!
> Also initdb works fine (/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/da
Jesse Denardo escribió:
> $ 9.2_dev/bin/pg_controldata data
> Latest checkpoint's NextMultiXactId: 2982
> Latest checkpoint's NextMultiOffset: 6479
So what's happening here is that the MultiXact 2982 lives in a SLRU page
that doesn't exist. pg_upgrade didn't copy the pg_multixact files from
t
Bruce Momjian escribió:
> On Tue, Jul 30, 2013 at 10:17:52AM -0400, Jesse Denardo wrote:
> So, first, this is new in 9.3, and second, it seems the comment "we need
> to reset pg_control so that the new server doesn't attempt to read
> multis older than the cutoff value&qu
Tom Jenkinson escribió:
> Hi Alban,
>
> I stripped down the code to a raw XA example using the latest
> postgres driver available in maven central. It demonstrates that
> regardless of what the codebase might suggest, it is certainly the
> case that postgres is returning XAER_RMERR in the scenario
Andres Freund wrote:
> On 2013-07-19 13:46:44 -0400, Alvaro Herrera wrote:
> > Sadly, this has performance implications, because what previously was
> > just an in-place check of bit flags has now become a function call.
>
> Well, the impact imo primarily comes from a
Andres Freund wrote:
> On 2013-07-19 13:46:44 -0400, Alvaro Herrera wrote:
> > Sadly, this has performance implications, because what previously was
> > just an in-place check of bit flags has now become a function call.
>
> Well, the impact imo primarily comes from a
levert...@googlemail.com wrote:
> START TRANSACTION ISOLATION LEVEL SERIALIZABLE;
> CREATE TABLE testing(
> x INTEGER PRIMARY KEY
> );
> INSERT INTO testing VALUES(1);
> SELECT * FROM testing WHERE x = 1 FOR UPDATE;
> SAVEPOINT test;
> UPDATE testing SET x = 2 WHERE x = 1;
> ROLLBACK TO test;
>
pg noob escribió:
> Alvaro,
>
> Is there a PostgreSQL bug number that I could refer to for this problem?
#8290 ?
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-bugs mailing lis
Jamey Poirier escribió:
>
> Thank you Alvaro. Yes, this explains it.
> It doesn't help to fix it but at least I know now that it's a known "feature".
> I'll have to see about coming up with a work-around as we likely won't get to
> 9.3 anytime soon.
pgn...@gmail.com escribió:
> I sent the following information to pgsql-general to ask if it is expected
> locking behavior. The only responses that I got said that the behavior is
> reproducible on 9.1 and 9.3 beta 2.
> Nobody said that this is expected locking behavior and I believe it to be a
>
Jeff Janes escribió:
> The bug was introduced in commit: 0ac5ad5... Improve concurrency of foreign
> key locking.
>
> I don't know what more to look into on this, so I'm cc Alvaro, the patch
> author.
Thanks, will look.
--
Álvaro Herrerahttp://www.2n
Tom Lane wrote:
> j...@pgexperts.com writes:
> > What happens is that we change various logging options in postgresql.conf,
> > then reload, and every so often, the settings don't seem to take effect even
> > though they are logged as being changed.
>
> FWIW, the "parameter changed" messages are l
Josh Kupershmidt escribió:
> On Thu, May 16, 2013 at 4:34 PM, hubert depesz lubaczewski
> wrote:
> > only when Pg is started with relative path, and restarted with absolute, the
> > problem shows.
> It has been a nuisance for me too. Possible patch for pg_ctl is in the next
> CF:
>
> http://
Tom Lane wrote:
> nico...@marchildon.net writes:
> > The man page says:
>
> > RETURN VALUE
> >The getpwnam() and getpwuid() functions return a pointer to a
> > passwd
> >structure, or NULL if the matching entry is not found or an
> > error
> >occurs. If an error
xavier.mouton-dub...@notalus.fr wrote:
> works well. But when I try to dump "other" schema
> pg_dump -s --schema="other" [...]
>
> I have this error:
> pg_dump: No matching schemas were found
>
> I have to surquote schema name to have it working
> pg_dump -s --schema="\"other\"" [...]
>
> see
Josh Berkus wrote:
> On 03/08/2013 07:27 PM, Alvaro Herrera wrote:
> > Josh Berkus wrote:
> >> Folks,
> >>
> >> This is one I've never seen before:
> >>
> >> => select generate_master_tables();
> >> WARNING: AbortTransaction
Josh Berkus wrote:
> Folks,
>
> This is one I've never seen before:
>
> => select generate_master_tables();
> WARNING: AbortTransaction while in COMMIT state
> PANIC: cannot abort transaction 9387287, it was already committed
Anything that causes an ERROR in the final stages of a transaction
c
dig...@126.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7840
> Logged by: digoal
> Email address: dig...@126.com
> PostgreSQL version: Unsupported/Unknown
> Operating system: CentOS 5.7 x64
I have pushed patches for these two problems, ple
dig...@126.com wrote:
> digoal=# select * from heap_page_items(get_raw_page('test', 0));
> lp | lp_off | lp_flags | lp_len | t_xmin | t_xmax | t_field3 | t_ctid |
> t_infomask2 | t_infomask | t_hoff | t_bits | t_oid
> ++--++++--++--
Pushed, thanks.
Jeff, Thomas, Jaime: please have a look and let me know what you think.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to you
Tom Lane escribió:
> Alvaro Herrera writes:
> > I disagree with this assessment, and propose the attached patch instead.
>
> +1 for this approach in HEAD ...
>
> > This is the patch for the master branch; I have not tried to backpatch
> > it yet. Conflicts are e
Alvaro Herrera escribió:
> On the other hand, running REASSIGN OWNED means to reassign ownership of
> objects to some other user. There is no reason this cannot be done to
> shared objects as well as local objects. I note, though, that REASSIGN
> OWNED's documentation mention
Jeff Janes escribió:
> Since back-branch releases are coming up, I think fe3b5eb08 and it's
> analogues in all branches should be reverted.
>
> The issue it was intended to solve was not really a bug in the first place,
> and this patch didn't solve it anyway. But it introduced new behavior (into
Bruce Momjian escribió:
>
> On Tue, Sep 4, 2012 at 02:01:54PM -0400, Bruce Momjian wrote:
> > On Tue, Sep 4, 2012 at 12:49:40PM -0500, Kevin Grittner wrote:
> > > Bruce Momjian wrote:
> > > > On Tue, Sep 4, 2012 at 12:11:53PM -0500, Kevin Grittner wrote:
> > >
> > > >> What do you think woul
Jeff Janes escribió:
> Since back-branch releases are coming up, I think fe3b5eb08 and it's
> analogues in all branches should be reverted.
Yes, I have this on my list of things to do before the next minor
release.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Developm
Tom Lane wrote:
>
> spam_ea...@gmx.net writes:
> > postgres=# create user testuser with password 'secret';
> > CREATE ROLE
> > postgres=# create database testdb owner testuser;
> > CREATE DATABASE
> > testdb=> drop owned by testuser;
> > ERROR: unrecognized object class: 1262
>
> I can reproduce
aanisi...@inbox.ru wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7722
> Logged by: Artem Anisimov
> Email address: aanisi...@inbox.ru
> PostgreSQL version: 9.2.1
> Operating system: Slackware Linux 14.0/amd64
> Description:
>
> The foll
Alvaro Herrera wrote:
> Here's a cleaned up version of this patch, for HEAD. (The patches for
> 9.1 and 9.2 required minor conflict fixes, but nothing substantial).
Committed.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training
Here's a cleaned up version of this patch, for HEAD. (The patches for
9.1 and 9.2 required minor conflict fixes, but nothing substantial).
The main difference from Dimitri's patch is that I added enough support
code so that AlterRelationNamespaceInternal() is always getting a valid
ObjectAddresse
Dave Vitek wrote:
> Heikki,
>
> It's happy about the overruns. It did flag an issue where the file
> descriptor can leak when the various early returns get taken.
This is a common problem with static analysers; they don't realise we
don't care about the leaked resource because the program is sh
Noah Misch escribió:
> Following an off-list ack from Alexander, here is that version. No functional
> differences from Alexander's latest version, and I have verified that it still
> fixes the original test case. I'm marking this Ready for Committer.
This seems good to me, but I'm not comforta
Andy Grimm escribió:
> Sorry that it's been a couple of weeks, but I have gotten around to
> working on a patch that address more of these concerns. The attached
> patch should
>
> 1) allow arbitrary length passwords to be read from a file via initdb --pwfile
> 2) allow the client to accept a pa
Nikolay escribió:
> Where can I found this path?
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=412a4295b5390cfe4fd5b9fc84a25c6e2d1aa0ad
You can also download the 9.1 snapshot from
ftp.postgresql.org/pub/snapshot/9.1, which should already contain this
patch.
--
Álvaro Herrera
Excerpts from wheelly's message of mar oct 02 05:49:27 -0300 2012:
> Where is a bug in PostgreSQL or in documentation?
I think it was a bug in the code. I have committed a patch that should
fix this problem.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 2
Excerpts from urvancevav's message of vie sep 28 05:58:42 -0300 2012:
> The following bug has been logged on the website:
>
> Bug reference: 7574
> Logged by: Andrei
> Email address: urvance...@gmail.com
> PostgreSQL version: 9.2.1
> Operating system: 3.2.0-31-generic #50-Ubun
Excerpts from Robert Haas's message of lun oct 01 21:02:54 -0300 2012:
> On Mon, Oct 1, 2012 at 12:57 PM, Fujii Masao wrote:
> > I believe many users are basically familiar with TCP keepalives and how to
> > specify it. So I think that this approach would be intuitive to users.
>
> My experience
Excerpts from Len Tanaka's message of jue sep 27 18:01:30 -0300 2012:
> Thank you for getting back. I noticed an update to 9.2.1. Will add log
> parameter and apply update. DB is not a particularly complex table and
> no foreign wrapping. Machine is older core duo though running OS X
> 10.6.8.
>
>
Excerpts from tanakalen's message of lun sep 17 06:00:05 -0300 2012:
> The following bug has been logged on the website:
>
> Bug reference: 7545
> Logged by: Len Tanaka
> Email address: tanaka...@gmail.com
> PostgreSQL version: 9.2.0
> Operating system: Mac OS X 10.6.8
> Descr
Excerpts from Dimitri Fontaine's message of lun sep 24 05:26:52 -0300 2012:
> Tom Lane writes:
> > Agreed. Quite aside from backwards-compatibility concerns, I think that
> > trying to avoid multiple dependency paths is doomed to failure.
>
> For a “DIRTT” approach to the problems, I think Álva
Excerpts from Dimitri Fontaine's message of mié sep 12 06:51:43 -0300 2012:
> Hi,
>
> Sorry for being late at the party… been distracted away…
Welcome ;-)
> > On Fri, Jun 22, 2012 at 10:37:10PM -0400, Tom Lane wrote:
> >> A bit of looking shows that ALTER EXTENSION SET SCHEMA calls
> >> AlterOb
Excerpts from Boy de Laat's message of jue sep 06 17:24:35 -0300 2012:
>
> At the time my backup starts i see much WAL logs being generated?
I guess we'd need to see what the generated WAL logs are, either with
xlogdump or XLOG_DEBUG turned on ...
--
Álvaro Herrerahttp://www.2nd
Excerpts from Tom Lane's message of jue sep 06 17:23:07 -0300 2012:
> Heikki Linnakangas writes:
> > On 06.09.2012 13:07, Robert Haas wrote:
> >> On Thu, Sep 6, 2012 at 3:55 PM, Tom Lane wrote:
> >>> Doesn't hint-bit setting cause WAL traffic these days?
>
> >> I sure as heck don't think so.
>
Excerpts from Tom Lane's message of vie ago 31 17:50:41 -0400 2012:
> Alvaro Herrera writes:
> > 2. During ALTER EXTENSION execution, skip moving objects that have
> > already been moved. Not really sure how this would be implemented;
>
> +1 for this approach. I&#
Excerpts from Alvaro Herrera's message of vie ago 31 16:25:40 -0400 2012:
> Excerpts from Tom Lane's message of vie ago 31 16:01:03 -0400 2012:
> > Alvaro Herrera writes:
> > > Here's a patch.
> >
> > Looks reasonable, but please try a little ha
Excerpts from Tom Lane's message of vie ago 31 16:01:03 -0400 2012:
> Alvaro Herrera writes:
> > Here's a patch.
>
> Looks reasonable, but please try a little harder on the comments for the
> new function --- IMO it should have a header comment that explains what
&
Excerpts from Alvaro Herrera's message of vie ago 31 12:26:50 -0400 2012:
> Excerpts from Tom Lane's message of vie ago 31 12:17:59 -0400 2012:
> > Alvaro Herrera writes:
> > > Aha, I see the bug. It seems the split for AlterObjectNamespace_oid
> > > related
Excerpts from Tom Lane's message of vie ago 31 12:17:59 -0400 2012:
> Alvaro Herrera writes:
> > Aha, I see the bug. It seems the split for AlterObjectNamespace_oid
> > related to tables was done at the wrong level: there should be a new
> > AlterTableNamespace_inter
Excerpts from Tom Lane's message of vie jun 22 22:37:10 -0400 2012:
> j...@pgexperts.com writes:
> > DROP and CREATE extension appear to work fine, but if you ALTER EXTENSION
> > postgis SET SCHEMA foo, it leaves a few relations behind.
>
> What it seems to be leaving behind is indexes ... also re
Excerpts from Tom Lane's message of jue ago 30 23:19:12 -0400 2012:
> Bruce Momjian writes:
> > On Fri, Jun 22, 2012 at 10:37:10PM -0400, Tom Lane wrote:
> >> j...@pgexperts.com writes:
> >>> DROP and CREATE extension appear to work fine, but if you ALTER EXTENSION
> >>> postgis SET SCHEMA foo, it
Excerpts from Bruce Momjian's message of lun ago 27 12:12:25 -0400 2012:
>
> Did we want this patch applied? Not enough demand?
I think it should be in the next commitfest for discussion. I don't see
any reason to reject it. I think it needs some fixes, though, so a
formal review process is c
Excerpts from Robert Haas's message of sáb ago 25 00:10:57 -0400 2012:
> > It looks sane to me in a quick once-over (bearing in mind I can't test
> > it). What's bothering you about the ereport calls?
>
> Well, 9.1 currently has:
>
> errmsg_internal("failed to enumerate network events: %i", (in
Excerpts from tigran.mkrtchyan's message of jue ago 23 10:37:02 -0400 2012:
> The following bug has been logged on the website:
>
> Bug reference: 7502
> Logged by: Tigran Mkrtchyan
> Email address: tigran.mkrtch...@desy.de
> PostgreSQL version: 9.1.1
> Operating system: Linux
Excerpts from Robert Haas's message of mar ago 21 14:54:28 -0400 2012:
> (BTW, I think commit 9b63e9869ffaa4d6d3e8bf45086a765d8f310f1c contains
> a thinko in one of the comments: shouldn't "a crock of the first
> water" be "a crock of the first order"?)
I was interested by that phrase when I saw
Excerpts from Todd Kover's message of mar ago 07 20:10:25 -0400 2012:
> Given this:
> --
> drop table IF EXISTS foo;
> drop table IF EXISTS foo_v26;
>
> create table foo (id serial not null, bar integer );
> alter table foo alter column id drop default;
>
> alter table foo rename to foo_v26;
Excerpts from jez.wain's message of mié jul 25 05:49:35 -0400 2012:
> ld: 0711-317 ERROR: Undefined symbol: .mbstowcs_l
> ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
> information.
>
> AIX7 supports the mbstowcs API but not mbstowcs_l. In
> src/include/pg_config.h I commen
Excerpts from Noah Misch's message of lun jul 16 11:12:01 -0400 2012:
> As a side question for the list, should we fix this differently in 9.2 to
> avoid forcing an initdb for the next beta? Perhaps have
> ATExecDropConstraint() only respect connoinherit for CONSTRAINT_CHECK?
My answer here was
Excerpts from Amit Kapila's message of jue jul 19 22:57:04 -0400 2012:
> From: Noah Misch [mailto:n...@leadboat.com]
> Sent: Thursday, July 19, 2012 5:23 PM
> On Tue, Jul 17, 2012 at 08:59:50AM +, Amit kapila wrote:
> >> Patch is attached with this mail.
>
> > Thanks. This patch is ready fo
Excerpts from runner.mei's message of mié jul 04 10:03:42 -0400 2012:
> The following bug has been logged on the website:
>
> Bug reference: 6716
> Logged by: runner.mei
> Email address: runner@gmail.com
> PostgreSQL version: 9.1.3
> Operating system: win2003
> Descriptio
Excerpts from Alvaro Herrera's message of mié abr 18 12:02:25 -0300 2012:
> Excerpts from emiliano.leporati's message of lun abr 16 06:21:53 -0300 2012:
>
> > failtest=# create extension citext;
> > CREATE EXTENSION
> > failtest=# create table foo(bar integ
Excerpts from Ryan Kelly's message of mar jun 19 16:20:58 -0400 2012:
> On Tue, Jun 19, 2012 at 07:49:20PM +, j...@tanga.com wrote:
> > View definition:
> > SELECT channels.id, channels.start_at, channels.end_at, channels.title
> >FROM channels
> >LEFT JOIN channels_products cp ON cp
Excerpts from Amit Kapila's message of mié jun 13 00:53:47 -0400 2012:
> > Unfortunately in src/backend/main/main.c it only does a cursory check
> > for --help and --version. So it would need to become a little more
> > complicated to scan for -C options at that stage. It's not too much
> > if y
Excerpts from Dave Page's message of mar jun 05 14:38:54 -0400 2012:
>
> On Sun, May 20, 2012 at 7:05 PM, Alvaro Herrera
> wrote:
> >> I have been installing PostgreSQL 9.1.3.2, and I've noted that 'creating
> >> database cluster' is too lo
Excerpts from grv87's message of sáb may 19 10:28:47 -0400 2012:
> The following bug has been logged on the website:
>
> Bug reference: 6652
> Logged by: Basil Peace
> Email address: gr...@yandex.ru
> PostgreSQL version: 9.1.3
> Operating system: Windows 7 x64
> Description:
Excerpts from tulio.carrasco's message of mar may 15 21:45:00 -0400 2012:
> In Spanish every vowel has the same precedence value even with or without
> any type of accent, so: a = á = ä = A = Á = Ä
> In which due dad column has the same value it uses the mum column and if
> they also have the sa
Excerpts from Matteo Beccati's message of lun abr 23 08:49:39 -0300 2012:
> Hi,
>
> I've recently seen a few errors on our continuous integration system
> during a test using a badly written partitioning trigger. The function
> was basically checking for the existence of the partition table at
Excerpts from emiliano.leporati's message of lun abr 16 06:21:53 -0300 2012:
> failtest=# create extension citext;
> CREATE EXTENSION
> failtest=# create table foo(bar integer);
> CREATE TABLE
> failtest=# reassign owned by ubik to dev;
> ERROR: unexpected classid 3079
Will fix.
--
Álvaro Her
Excerpts from mit's message of jue abr 12 14:37:48 -0300 2012:
> The following bug has been logged on the website:
>
> Bug reference: 6585
> Logged by: Andrey Mitroshin
> Email address: m...@akamit.com
> PostgreSQL version: 9.1.3
> Operating system: AIX 7.1.0
> Description:
Excerpts from Bruce Momjian's message of lun abr 09 15:13:10 -0300 2012:
> On Mon, Apr 09, 2012 at 10:10:34AM -0400, Robert Haas wrote:
> > This complaint appears to be accurate. I think we should go ahead and
> > remove that mention.
>
> Agreed; removed with the attached patch. I didn't both
Excerpts from Alexander LAW's message of mar mar 20 16:50:14 -0300 2012:
> Thanks, I've understood your point.
> Please look at the patch. It implements the first way and it makes psql
> work too.
Great, thanks. Hopefully somebody with Windows-compile abilities will
have a look at this.
--
Á
Excerpts from Aren Cambre's message of dom mar 18 23:39:16 -0300 2012:
> Thanks. I am running this on 1 year old hardware on a wholly-encrypted C
> drive, encrypted with TrueCrypt. I suspect that I would have been alerted
> already with that or SMART if I had hardware issues?
That sounds excessiv
Excerpts from Alex Hunsaker's message of mié mar 07 01:08:25 -0300 2012:
> On Sat, Mar 3, 2012 at 12:19, wrote:
> Yeah, there were some optimization done for 9.1 to try and make calls
> a bit faster. The problem is we are fetching "_TD" not "main::_TD",
> which means we try to find and use $_TD
Excerpts from Alexander LAW's message of dom mar 18 06:04:51 -0300 2012:
> I see two ways to resolve the issue.
> First is to use CharToOemBuff when writing a string to the "con" and
> OemToCharBuff when reading an input from it.
> The other is to always use stderr/stdin for Win32 as it was done
Excerpts from exclusion's message of sáb mar 03 15:44:37 -0300 2012:
> I'm using postgresSQL in Windows with Russian locale and get unreadable
> messages when the postgres utilities prompting me for input.
> Please look at the screenshot:
> http://oi44.tinypic.com/aotje8.jpg
> (The psql writes th
Excerpts from Tom Lane's message of mié mar 07 17:31:32 -0300 2012:
> This probably could be done for rowtype columns as well, but nobody has
> collected the necessary round tuits. I think there was some fear of
> locking/deadlock issues, too.
It's probably easy to do if you require it to be ma
Excerpts from vygen's message of lun mar 05 09:14:26 -0300 2012:
> Messages to sdterr does not appear at all anywhere. I prefer syslog because
> of pgfouine.
FWIW I think pgfouine is perfectly capable of using stderr logs now.
--
Álvaro Herrera
The PostgreSQL Company - Command Prompt, Inc.
Po
Excerpts from rikard.pavelic's message of sáb feb 25 10:23:18 -0300 2012:
> But I would expect second alter to pass and enforcing not null and default
> when adding this column in table and not enforcing not null and default when
> adding into composite type for another table.
>
> Is this by des
Excerpts from Susanne Ebrecht's message of sáb feb 18 18:11:54 -0300 2012:
> Output in German:
> i | integer | not null Vorgabewert nextval('t_i_seq'::regclass)
>
> Output in French:
> i | integer | non NULL Par défaut, nextval('t_i_seq'::regclass)
>
> Output in Spanish:
> i |
Excerpts from Bruce Momjian's message of vie feb 03 15:52:29 -0300 2012:
> Actually, thinking more about this, the old pg_upgrade didn't use pg_ctl
> wait/-w mode, but rather kept trying to connect until the server was up.
> Once pg_ctl -w worked in more cases in PG 9.1, the new pg_upgrade
> star
Excerpts from Tom Lane's message of mié feb 01 18:06:27 -0300 2012:
> Robert Haas writes:
> >>> No, I wasn't thinking about a tuple descriptor mismatch. I was
> >>> imagining that the page contents themselves might be in flux while
> >>> we're trying to read from it.
>
> > It would be nice to ge
Excerpts from Duncan Rance's message of mié feb 01 17:43:48 -0300 2012:
> I mentioned in the bug report that I has asserts in places were t_hoff is
> set. I've been doing it like so:
>
> if (hoff % 4 != 0) {
> elog(ERROR, "wrong hoff: %d",hoff);
> abort();
> }
>
> I've been sitting here wa
Excerpts from Bridget Frey's message of lun ene 30 18:59:08 -0300 2012:
> Anyway, here goes...
Maybe a "bt full" could give more insight into what's going on ...
> #0 0x003a83e30265 in raise () from /lib64/libc.so.6
> #1 0x003a83e31d10 in abort () from /lib64/libc.so.6
> #2 0x000
Excerpts from Andy Grimm's message of sáb ene 28 14:32:24 -0300 2012:
> Perhaps I should just submit the patch to pgsql-hackers ? I'm new to
> the pgsql bug interaction process, so my apologies if filing a bug was
> not the appropriate way to present the issue. I get Internal Server
> Error mes
Excerpts from Heikki Linnakangas's message of jue ene 19 07:25:36 -0300 2012:
> Frankly that's such a rare corner case that I'm not very enthusiastic
> about fixing it. One idea would be to look up the type's b-tree sort
> operators, and pick the equality operator from there. But point datatype
Excerpts from maxim.boguk's message of mar ene 10 23:00:59 -0300 2012:
> The following bug has been logged on the website:
>
> Bug reference: 6393
> Logged by: Maxim Boguk
> Email address: maxim.bo...@gmail.com
> PostgreSQL version: 9.0.6
> Operating system: Linux Ubuntu
> De
Excerpts from Tom Lane's message of lun ene 02 17:28:33 -0300 2012:
> Anyway the immediate question is which errnos are reasonable for copydir
> to ignore. Just looking at the standard's description of fsync's error
> conditions:
>
> The fsync() function shall fail if:
> [EBADF]
> T
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
> PostgreSQL version: 9.1.2
> Operating system: Kubuntu Linux 10.10
> Descrip
1 - 100 of 764 matches
Mail list logo
