Hi,
On Tue, 2012-09-25 at 20:42 -0400, Robert Haas wrote:
> It seems therefore that REINDEX + VACUUM with
> vacuum_freeze_table_age=0 is not quite sufficient to recover from this
> problem. If your index has come to contain a circularity, vacuum will
> fail to terminate, and you'll need to drop
Forget to mention, that:
- VACUUM is running on the master;
- current state is unchanged for 20 hours.
2012/9/26 Виктор Егоров :
> I'm afraid I'm exactly in this situation now.
>
> Last entry from the 9.1.6 recommended VACUUM (FREEZE, VERBOSE, ANALYZE) was:
> INFO: "meta_version_chunks": found 55
I'm afraid I'm exactly in this situation now.
Last entry from the 9.1.6 recommended VACUUM (FREEZE, VERBOSE, ANALYZE) was:
INFO: "meta_version_chunks": found 55363 removable, 32566245 nonremovable
row versions in 450292 out of 450292 pages
DETAIL: 0 dead row versions cannot be removed yet.
There
On Wed, Sep 26, 2012 at 12:17 AM, Daymel Bonne Solís wrote:
> Hello hackers:
>
> I need a list of all triggers created in my database, but the view
> system_information.triggers does not show truncate triggers, but it does for
> insert, update and delete triggers.
>
> The same problem is found in
Hello hackers:
I need a list of all triggers created in my database, but the view
system_information.triggers does not show truncate triggers, but it does
for insert, update and delete triggers.
The same problem is found in versions 9.1 and 9.2.
Regards.
10mo. ANIVERSARIO DE LA CREACION DE
On Tue, Sep 25, 2012 at 5:30 PM, Peter Eisentraut wrote:
> I haven't followed the details of the htup header reorganization, but I
> have noticed that a number of external extension modules will be broken
> because of the move of GETSTRUCT() and to a lesser extent
> heap_getattr(). Of course some
On Mon, 2012-09-17 at 23:10 -0400, Tom Lane wrote:
> > I had suggested to put it into src/include/port/linux.h
>
> OK, that's probably reasonable.
It turns out that doesn't work because port.h is included after all the
interesting libc header files (stdio.h etc.).
I think the best place to put i
Patch looks good, all concerns that had been raised previously have
been addressed in this version of the patch.
The only thing that IMO needs to change is a stylistic issue:
if (fout->remoteVersion >= 80200)
{
[...]
(fout->remoteVersion >= 80400) ?
"pg_catalog.pg_get_function_identity_ar
On Tue, Sep 25, 2012 at 10:23 AM, Tom Lane wrote:
> Andrew Dunstan writes:
>> Given your previous comments, perhaps we could just start handing out
>> Oids (if there is any demand) numbered, say, 9000 and up. That should
>> keep us well clear of any existing use.
>
> No, I think you missed my poi
On 09/25/2012 08:35 PM, Peter Eisentraut wrote:
On Tue, 2012-09-25 at 18:22 -0400, Tom Lane wrote:
Actually, after reading another message you sent, I thought you were
going to respond that your proposed transforms feature would cover it.
I had thought about this some time ago, but it's cleare
On Fri, Sep 21, 2012 at 10:41 AM, Andres Freund wrote:
> Hrm. I retract my earlier statement about the low likelihood of corruption due
> to this.
Yeah. :-(
We've recently had at least one report of autovacuum failing to
terminate due to a series of index pages forming a circular loop, and
at l
On Wed, Sep 26, 2012 at 4:42 AM, Dimitri Fontaine wrote:
> Simon Riggs writes:
> > For me, the Postgres user interface should include
> > * REINDEX CONCURRENTLY
> > * CLUSTER CONCURRENTLY
> > * ALTER TABLE CONCURRENTLY
> > and also that autovacuum would be expanded to include REINDEX and
> > CLUS
On Mon, 2012-09-24 at 21:18 -0700, Daniel Farina wrote:
> The gap between
> pre-JSON-in-the-standard-library in Python, Ruby, et al and
> post-JSON-in-stdlib was much smaller.
Except in Python they renamed the thing.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To mak
On Tue, 2012-09-25 at 18:22 -0400, Tom Lane wrote:
> Actually, after reading another message you sent, I thought you were
> going to respond that your proposed transforms feature would cover it.
I had thought about this some time ago, but it's clearer to think of
casts as associating two types, ve
I haven't followed the details of the htup header reorganization, but I
have noticed that a number of external extension modules will be broken
because of the move of GETSTRUCT() and to a lesser extent
heap_getattr(). Of course some #ifdefs can fix that, but it seems
annoying to make everyone do t
John:
Who has the money for oracle RAC or funding arrogant bastard Oracle CEO
Ellison to purchase another island?
Postgres needs CHEAP, easy to setup, self healing,
master-master-master-master and it needs it yesterday.
I was able to patch the 9.2.0 code base in 1 day and change my entire
On 09/26/2012 12:06 AM, Peter Eisentraut wrote:
On 9/25/12 5:58 PM, Tom Lane wrote:
Yes ... but I really don't want to go down the path of treating those as
new type properties; it doesn't scale. (And please don't tell me that
JSON is the last word in container types and there will never be
req
On 09/25/2012 12:13 PM, Heikki Linnakangas wrote:
On 25.09.2012 12:19, Hitoshi Harada wrote:
On Tue, Sep 25, 2012 at 1:06 AM, Simon Riggs
wrote:
On 24 September 2012 21:26, Andrew Dunstan wrote:
Well, an obvious case is how record_to_json handles fields. If it
knows
nothing about the type a
On 09/25/12 11:01 AM, m...@rpzdesign.com wrote:
At some point, every master - slave replicator gets to the point where
they need
to start thinking about master-master replication.
master-master and transactional integrity are mutually exclusive, except
perhaps in special cases like Oracle
Peter Eisentraut writes:
> On 9/25/12 5:58 PM, Tom Lane wrote:
>> Can we define these functions as being the cast-from-foo-to-json and
>> cast-from-foo-to-xml functions? That would let us use the existing cast
>> infrastructure to manage them.
> Sounds attractive, but there might be some problem
On Tue, Sep 25, 2012 at 11:01 AM, m...@rpzdesign.com wrote:
> Amit:
>
> At some point, every master - slave replicator gets to the point where they
> need
> to start thinking about master-master replication.
Even in a master-master system, the ability to cleanly swap leaders
managing a member of
On 9/25/12 5:58 PM, Tom Lane wrote:
> Yes ... but I really don't want to go down the path of treating those as
> new type properties; it doesn't scale. (And please don't tell me that
> JSON is the last word in container types and there will never be
> requests for any more of these.)
Yeah, I didn
On 9/25/12 9:18 AM, Andrew Dunstan wrote:
> No, the difficulty (or at least the first difficulty) is in having the
> code recognize that it has an hstore at all. The code picks apart the
> record field by field at run time and takes various actions depending on
> the field's type. For any type it d
On 9/25/12 6:13 AM, Heikki Linnakangas wrote:
> That brings us to another question: should the cast be part of the
> hstore extension, or json? (json is built-in, but imagine for a moment
> that it was an extension, too, so that there was a choice). IIRC someone
> started a discussion on that recen
Peter Eisentraut writes:
> On 9/24/12 10:26 PM, Andrew Dunstan wrote:
>> Well, an obvious case is how record_to_json handles fields. If it knows
>> nothing about the type all it can do is output the string value. That
>> doesn't work well for types such as hstore. If it could reliably
>> recognize
On 9/25/12 1:11 AM, Hitoshi Harada wrote:
> Say, if plv8
> wants to convert hstore into a javascript object. It is arbitrary for
> users to define such a function that accepts hstore as arguments, but
> how does plv8 know the input is actually hstore?
That's what the proposed transforms feature w
On 9/24/12 11:39 PM, Tom Lane wrote:
> My recollection of the PGCon discussion is that people wanted to allow
> client-side code to hard-wire type OIDs for add-on types, in more or
> less the same way that things like JDBC know that "25" is "text".
If I write a custom uint type and want to explain
On 9/24/12 10:26 PM, Andrew Dunstan wrote:
> Well, an obvious case is how record_to_json handles fields. If it knows
> nothing about the type all it can do is output the string value. That
> doesn't work well for types such as hstore. If it could reliably
> recognize a field as an hstore it might w
Is there any reason we don't use ldap_err2string() to get readable error
messages from LDAP, instead something like "error code 49"? It's
already used in some places, so it's apparently OK to use. Proposed
patch attached.
diff --git a/src/backend/libpq/auth.c b/src/backend/libpq/auth.c
index c765
Tom Lane writes:
> Andrew Dunstan writes:
>> Given your previous comments, perhaps we could just start handing out
>> Oids (if there is any demand) numbered, say, 9000 and up. That should
>> keep us well clear of any existing use.
>
> No, I think you missed my point entirely: handing out OIDs a
Simon Riggs writes:
> For me, the Postgres user interface should include
> * REINDEX CONCURRENTLY
> * CLUSTER CONCURRENTLY
> * ALTER TABLE CONCURRENTLY
> and also that autovacuum would be expanded to include REINDEX and
> CLUSTER, renaming it to automaint.
FWIW, +1 to all those user requirements,
Hi,
2012/08/12 7:11, Jeff Janes wrote:
On Sat, Jul 28, 2012 at 3:33 PM, Jeff Janes wrote:
On Sat, Jul 7, 2012 at 9:17 PM, Satoshi Nagayasu wrote:
Hi,
Jeff Janes has pointed out that my previous patch could hold
a number of the dirty writes only in single local backend, and
it could not hold
Amit:
At some point, every master - slave replicator gets to the point where
they need
to start thinking about master-master replication.
Instead of getting stuck in the weeds to finally realize that
master-master is the ONLY way
to go, many developers do not start out planning for master - m
On Tue, Sep 25, 2012 at 09:18:30AM -0400, Andrew Dunstan wrote:
> >I'm not at all familiar with record_to_json or the json datatype,
> >but wouldn't it be appropriate to create a cast from hstore to
> >json to handle that case?
>
> No, the difficulty (or at least the first difficulty) is in having
On 09/25/2012 12:14 PM, Tom Lane wrote:
Alvaro Herrera writes:
Excerpts from Hitoshi Harada's message of mar sep 25 02:11:14 -0300 2012:
Of course you can
look up type name conlusting SysCache and see if the type name is
"hstore", but it's expensive to do it for every function invocation,
so
On Tue, Sep 25, 2012 at 11:05 PM, Simon Riggs wrote:
> On 21 September 2012 02:25, Heikki Linnakangas
> wrote:
>> On 03.07.2012 15:13, Robert Haas wrote:
>>>
>>> On the substance of the patch, I believe the reason why this is
>>> currently disallowed is because the TLI is implicitly taken from t
Alvaro Herrera writes:
> Excerpts from Hitoshi Harada's message of mar sep 25 02:11:14 -0300 2012:
>> Of course you can
>> look up type name conlusting SysCache and see if the type name is
>> "hstore", but it's expensive to do it for every function invocation,
>> so caching the hstore's oid in plv
> On Tuesday, September 25, 2012 7:30 PM Heikki Linnakangas wrote:
> On 24.09.2012 13:57, Amit kapila wrote:
> > Rebased version of patch based on latest code.
>
> When HOT was designed, we decided that heap_update needs to compare the
> old and new attributes directly, with memcmp(), to determine
Excerpts from Hitoshi Harada's message of mar sep 25 02:11:14 -0300 2012:
> Of course you can
> look up type name conlusting SysCache and see if the type name is
> "hstore", but it's expensive to do it for every function invocation,
> so caching the hstore's oid in plv8 is the current workaround,
Tom,
I'm fine with submitting highly focused patches first. I was just
explaining my end-goal. Still I will need time to patch, compile, and
test before submitting so you're not going to see any output from me
for a few days. That's all assuming my employer can leave me alone
long enough to focus
Unless I misread the code, the tar format and streaming xlog are
mutually exclusive. Considering my normal state of fatigue it's not
unlikely. I don't want to have to set my wal_keep_segments
artificially high just for the backup
On Tue, Sep 25, 2012 at 10:05 AM, Marko Tiikkaja wrote:
> On 9/25/1
On 09/25/2012 10:23 AM, Tom Lane wrote:
Andrew Dunstan writes:
Given your previous comments, perhaps we could just start handing out
Oids (if there is any demand) numbered, say, 9000 and up. That should
keep us well clear of any existing use.
No, I think you missed my point entirely: handing
Hi,
I just performed a test upgrade from 9.1 to 9.2, and used --new-port
variable. However, the analyze_new_cluster.sh does not include the new
port, thus when I run it, it fails. Any chance to add the port number to
the script?
Also, is it worth to add the value specified in --new-bindir as a p
Brian Weaver writes:
> If you're willing to wait a bit on me to code and test my extensions
> to pg_basebackup I will try to address some of the deficiencies as
> well add new features.
I think it's a mistake to try to handle these issues in the same patch
as feature extensions. If you want to s
Andrew Dunstan writes:
> Given your previous comments, perhaps we could just start handing out
> Oids (if there is any demand) numbered, say, 9000 and up. That should
> keep us well clear of any existing use.
No, I think you missed my point entirely: handing out OIDs at the top
of the manual as
On 21 September 2012 02:25, Heikki Linnakangas wrote:
> On 03.07.2012 15:13, Robert Haas wrote:
>>
>> On the substance of the patch, I believe the reason why this is
>> currently disallowed is because the TLI is implicitly taken from the
>> running system, and on the standby that might be the wron
On 9/25/12 3:38 PM, Brian Weaver wrote:
I want
to modify pg_basebackup to include the WAL files in the tar output.
Doesn't pg_basebackup -x do exactly that?
Regards,
Marko Tiikkaja
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
h
On 24.09.2012 13:57, Amit kapila wrote:
Rebased version of patch based on latest code.
When HOT was designed, we decided that heap_update needs to compare the
old and new attributes directly, with memcmp(), to determine whether any
of the indexed columns have changed. It was not deemed infeas
> On Tuesday, September 25, 2012 6:29 PM Heikki Linnakangas wrote:
> On 25.09.2012 10:08, Heikki Linnakangas wrote:
> > On 24.09.2012 16:33, Amit Kapila wrote:
> >> In any case, it will be better if you can split it into multiple
> patches:
> >> 1. Having new functionality of "Switching timeline ov
Tom,
I actually plan on doing a lot of work on the frontend pg_basebackup
for my employer. pg_basebackup is 90% of the way to a solution that I
need for doing backups of *large* databases while allowing the
database to continue to work. The problem is a lack of secondary disk
space to save a repli
On 09/24/2012 11:39 PM, Tom Lane wrote:
My recollection of the PGCon discussion is that people wanted to allow
client-side code to hard-wire type OIDs for add-on types, in more or
less the same way that things like JDBC know that "25" is "text".
That's not unreasonable, since the alternatives a
On Tuesday, September 25, 2012 6:27 PM Simon Riggs wrote :
> On 24 September 2012 04:00, Heikki Linnakangas
> wrote:
> > On 18.07.2012 16:47, Amit kapila wrote:
> >>
> >> Patch implementing the design in below mail chain is attached with
> this
> >> mail.
> >
> >
> > This patch copies the ReadReco
As part of the PostgreSQL Development process, we agreed that
everybody that supplies a patch would also review a patch. Doing that
gives the process balance and avoids focusing on particular
individuals for review. It's Peer Review, not Free Review.
In Sept 2012 review process we have 5 people do
On 09/25/2012 06:13 AM, Heikki Linnakangas wrote:
On 25.09.2012 12:19, Hitoshi Harada wrote:
On Tue, Sep 25, 2012 at 1:06 AM, Simon Riggs
wrote:
On 24 September 2012 21:26, Andrew Dunstan wrote:
Well, an obvious case is how record_to_json handles fields. If it
knows
nothing about the type
On Tuesday, September 25, 2012 01:58:31 AM Andres Freund wrote:
> On Monday, September 24, 2012 01:37:59 PM Andres Freund wrote:
> > On Monday, September 24, 2012 01:27:54 PM Andres Freund wrote:
> > > Problem 2: undroppable indexes:
> > >
> > >
> > > Session 1:
> > > CREATE TABLE test_drop_concu
On Tue, Sep 25, 2012 at 12:22:43PM +0800, Rural Hunter wrote:
> >OK, that is good to know. I developed the attached C program that does
> >the setlocale canonical test. On Debian Squeeze, I could not see any
> >change: if I pass en_US.UTF-8, I get en_US.UTF-8 returned; if I pass
> >en_US.UTF8,
On 24 September 2012 04:00, Heikki Linnakangas wrote:
> On 18.07.2012 16:47, Amit kapila wrote:
>>
>> Patch implementing the design in below mail chain is attached with this
>> mail.
>
>
> This patch copies the ReadRecord() function and a bunch of related functions
> from xlog.c into pg_resetxlog.
On Tue, Sep 25, 2012 at 5:55 PM, Andres Freund wrote:
> On Tuesday, September 25, 2012 04:37:05 AM Michael Paquier wrote:
> > On Tue, Sep 25, 2012 at 8:13 AM, Andres Freund >wrote:
> > Could you clarify what do you mean here by cleanup?
> > I am afraid I do not get your point here.
>
> Sorry, was
On 25.09.2012 14:10, Amit Kapila wrote:
On Tuesday, September 25, 2012 12:39 PM Heikki Linnakangas wrote:
On 24.09.2012 16:33, Amit Kapila wrote:
On Tuesday, September 11, 2012 10:53 PM Heikki Linnakangas wrote:
I've been working on the often-requested feature to handle timeline
changes ove
On Tuesday, September 25, 2012 12:39 PM Heikki Linnakangas wrote:
> On 24.09.2012 16:33, Amit Kapila wrote:
> > On Tuesday, September 11, 2012 10:53 PM Heikki Linnakangas wrote:
> >> I've been working on the often-requested feature to handle timeline
> >> changes over streaming replication. At th
On 25.09.2012 12:19, Hitoshi Harada wrote:
On Tue, Sep 25, 2012 at 1:06 AM, Simon Riggs wrote:
On 24 September 2012 21:26, Andrew Dunstan wrote:
Well, an obvious case is how record_to_json handles fields. If it knows
nothing about the type all it can do is output the string value. That
doesn'
On Tue, Sep 25, 2012 at 1:06 AM, Simon Riggs wrote:
> On 24 September 2012 21:26, Andrew Dunstan wrote:
>> Well, an obvious case is how record_to_json handles fields. If it knows
>> nothing about the type all it can do is output the string value. That
>> doesn't work well for types such as hstore
On Tuesday, September 25, 2012 04:37:05 AM Michael Paquier wrote:
> On Tue, Sep 25, 2012 at 8:13 AM, Andres Freund wrote:
> > On Tuesday, September 25, 2012 12:55:35 AM Josh Berkus wrote:
> > > On 9/24/12 3:43 PM, Simon Riggs wrote:
> > > > On 24 September 2012 17:36, Josh Berkus wrote:
> > >
On 09/25/2012 04:26 AM, Andrew Dunstan wrote:
On 09/24/2012 09:37 PM, Peter Eisentraut wrote:
On Mon, 2012-09-24 at 18:59 -0400, Andrew Dunstan wrote:
This rather overdue mail arises out the developer's meeting back in
May, where we discussed an item I raised suggesting an Oid registry.
The i
On 24 September 2012 21:26, Andrew Dunstan wrote:
>
> On 09/24/2012 09:37 PM, Peter Eisentraut wrote:
>>
>> On Mon, 2012-09-24 at 18:59 -0400, Andrew Dunstan wrote:
>>>
>>> This rather overdue mail arises out the developer's meeting back in
>>> May, where we discussed an item I raised suggesting a
On 24.09.2012 22:13, Gavin Flower wrote:
On 25/09/12 02:41, Heikki Linnakangas wrote:
Multiple files within an include directory are processed in filename
order. The filenames are ordered by C locale rules, ie. numbers before
letters, and uppercase letters before lowercase ones.
Even I can und
On 24.09.2012 16:33, Amit Kapila wrote:
On Tuesday, September 11, 2012 10:53 PM Heikki Linnakangas wrote:
I've been working on the often-requested feature to handle timeline
changes over streaming replication. At the moment, if you kill the
master and promote a standby server, and you have anoth
67 matches
Mail list logo
