I'm proposing this now as a possible GSoC project:
In 1-byte character encodings (i.e. not UTF-8), SUBSTR() is optimised
to allow seeking straight to the exact slice when retrieving a large
toasted value. This reduces I/O considerably when you have large
toasted values since it is an O(1) action r
Stephen Frost writes:
> * Marko Kreen (mark...@gmail.com) wrote:
>> On Sat, May 04, 2013 at 10:57:44PM +0200, Dimitri Fontaine wrote:
>> > Other than adminpack, I know of PGQ installing their objects in
>> > pg_catalog. They only began doing that when switching to the CREATE
>> > EXTENSION facilit
On 05/14/2013 10:05 AM, Simon Riggs wrote:
> I'm proposing this now as a possible GSoC project:
>
> In 1-byte character encodings (i.e. not UTF-8), SUBSTR() is optimised
> to allow seeking straight to the exact slice when retrieving a large
> toasted value. This reduces I/O considerably when you ha
On Tue, May 14, 2013 at 5:27 AM, Peter Eisentraut wrote:
> On Tue, 2013-05-14 at 04:12 +0300, Marti Raudsepp wrote:
>> It's caused by this common pattern in extension makefiles:
>> DATA = $(wildcard sql/*--*.sql) sql/$(EXTENSION)--$(EXTVERSION).sql
> What is the point of this? Why have the wildc
On Tue, May 14, 2013 at 09:29:38AM +0200, Dimitri Fontaine wrote:
> Stephen Frost writes:
> > * Marko Kreen (mark...@gmail.com) wrote:
> >> On Sat, May 04, 2013 at 10:57:44PM +0200, Dimitri Fontaine wrote:
> >> > Other than adminpack, I know of PGQ installing their objects in
> >> > pg_catalog. Th
On Sunday, May 12, 2013 4:53 AM Robert Haas wrote:
> On Sat, May 11, 2013 at 12:27 PM, Tom Lane wrote:
> > By the time you've got an expression tree, the problem is mostly
> solved,
> > at least so far as parser extension is concerned.
>
> Right.
>
> > More years ago than I care to admit, I work
* Dimitri Fontaine (dimi...@2ndquadrant.fr) wrote:
> I'm not sure I agree with that view about pg_catalog. Sometimes we talk
> about moving some parts of core in pre-installed extensions instead, and
> if we do that we will want those extensions to install themselves into
> pg_catalog.
For my part
On 2013-05-13 21:04:06 -0400, Stephen Frost wrote:
> * Marko Kreen (mark...@gmail.com) wrote:
> > On Sat, May 04, 2013 at 10:57:44PM +0200, Dimitri Fontaine wrote:
> > > Other than adminpack, I know of PGQ installing their objects in
> > > pg_catalog. They only began doing that when switching to th
Le mardi 14 mai 2013 10:17:13, Marti Raudsepp a écrit :
> On Tue, May 14, 2013 at 5:27 AM, Peter Eisentraut wrote:
> > On Tue, 2013-05-14 at 04:12 +0300, Marti Raudsepp wrote:
> >> It's caused by this common pattern in extension makefiles:
> >> DATA = $(wildcard sql/*--*.sql) sql/$(EXTENSION)--$(E
Marti Raudsepp writes:
> all: sql/$(EXTENSION)--$(EXTVERSION).sql
>
> sql/$(EXTENSION)--$(EXTVERSION).sql: sql/$(EXTENSION).sql
> cp $< $@
That's a recipe for problems. Each time I meet with such a construct in
an extension's Makefile I propose an hard coded alternative. We're
speaking of
On 5/13/13 10:58 PM, Andrew Dunstan wrote:
> I'm not sure why the wildcard is a bad idea - don't we want any present
> update sql files to be installed?
Generally, wildcards in makefiles are a bad idea because you will then
not discover any broken tarballs and checkouts. The users will just
insta
Today we have seen this on our testing database instance:
ERROR: could not open file "base/16416/291498116.3" (target block 431006):
No such file or directory
That database get's created by rsyncing the LVM snapshot of the standby,
which is a readonly backup of proddb
using streaming replication
On 5/14/13 4:17 AM, Marti Raudsepp wrote:
> On Tue, May 14, 2013 at 5:27 AM, Peter Eisentraut wrote:
>> On Tue, 2013-05-14 at 04:12 +0300, Marti Raudsepp wrote:
>>> It's caused by this common pattern in extension makefiles:
>>> DATA = $(wildcard sql/*--*.sql) sql/$(EXTENSION)--$(EXTVERSION).sql
>
On 5/14/13 7:50 AM, Dimitri Fontaine wrote:
> Marti Raudsepp writes:
>> > all: sql/$(EXTENSION)--$(EXTVERSION).sql
>> >
>> > sql/$(EXTENSION)--$(EXTVERSION).sql: sql/$(EXTENSION).sql
>> > cp $< $@
> That's a recipe for problems. Each time I meet with such a construct in
> an extension's Ma
HI.
Thanks, Heikki, for the answer on google-melange. For some reason i didn't
receive email notification, so I saw this answer only today.
> Do you have access to a server you can use to perform those tests? (...)
Yes, i have. I am maintaining MPI cluster in my university, so it is not a
prob
* Andres Freund (and...@2ndquadrant.com) wrote:
> I don't disagree, but how is that relevant for fixing the issue at hand?
> We still need to fix restores that currently target the wrong schema in
> a backward compatible manner?
On this, I agree w/ Tom that we should put that check back into place
On Tue, May 14, 2013 at 12:51 AM, Michael Paquier
wrote:
>> I'm not sure what the specific answer here should look like. Simply
>> having a
>> CREATE FUNCTION ... PARALLEL_IS_FINE flag is not entirely satisfying,
>> because
>> the rules are liable to loosen over time.
>
> Having a flag would be e
On Tue, May 14, 2013 at 4:30 PM, Stas Kelvich wrote:
> * Don't do cube with type support
> Eventually, there is different ways of reducing R-Tree size. For
> example we can store relative coordinates with dynamic size of MBR (VRMBR),
> instead of absolute coordinates with fixed sized MBR.
On 05/14/2013 07:59 AM, Peter Eisentraut wrote:
On 5/14/13 4:17 AM, Marti Raudsepp wrote:
On Tue, May 14, 2013 at 5:27 AM, Peter Eisentraut wrote:
On Tue, 2013-05-14 at 04:12 +0300, Marti Raudsepp wrote:
It's caused by this common pattern in extension makefiles:
DATA = $(wildcard sql/*--*.sq
On May 14, 2013, at 4:53 PM, Alexander Korotkov wrote:
> Sounds promising. Did you examine how this technique can fit into GiST? In
> current GiST interface methods don't have access to parent entries.
No, i didn't examine it yet. Anyway in this technique lots of changes should be
performed to
On 14.05.2013 14:57, Benedikt Grundmann wrote:
Today we have seen this on our testing database instance:
ERROR: could not open file "base/16416/291498116.3" (target block 431006):
No such file or directory
That database get's created by rsyncing the LVM snapshot of the standby,
which is a read
As discussed and concluded in mail thread
(http://www.postgresql.org/message-id/006f01ce34f0$d6fa8220$84ef8660$@kapila
@huawei.com), for moving unused buffer's to freelist end,
I having implemented the idea and taken some performance data.
In the attached patch, bgwriter/checkpointer moves
It's on the production database and the streaming replica. But not on the
snapshot.
production
-rw--- 1 postgres postgres 312778752 May 13 21:28
/database/postgres/base/16416/291498116.3
streaming replica
-rw--- 1 postgres postgres 312778752 May 13 23:50
/database/postgres/base/16416/291
On Mon, May 13, 2013 at 4:31 PM, Dmitry Koterov wrote:
> Could you please provide a bit more detailed explanation on how it works?
>
> And how could postgres write at the middle of archiving files during an
> active pg_start_backup? if it could, here might be a case when a part of
> archived data
On Mon, May 13, 2013 at 07:55:16PM +0100, Simon Riggs wrote:
> On 13 May 2013 15:28, Noah Misch wrote:
>
> > The heavyweight locking mechanism will need to be aware of the association
> > between the master and its workers.
>
> Not sure I can see why that would be true.
>
> ISTM that the worker
Le mardi 14 mai 2013 10:17:13, Marti Raudsepp a écrit :
> On Tue, May 14, 2013 at 5:27 AM, Peter Eisentraut wrote:
> > On Tue, 2013-05-14 at 04:12 +0300, Marti Raudsepp wrote:
> >> It's caused by this common pattern in extension makefiles:
> >> DATA = $(wildcard sql/*--*.sql) sql/$(EXTENSION)--$(E
On Mon, May 13, 2013 at 09:52:43PM +0200, Kohei KaiGai wrote:
> 2013/5/13 Noah Misch
> > The choice of whether to parallelize can probably be made a manner similar
> > to
> > the choice to do an external sort: the planner guesses the outcome for
> > costing
> > purposes, but the actual decision is
On Tue, May 14, 2013 at 01:51:42PM +0900, Michael Paquier wrote:
> On Mon, May 13, 2013 at 11:28 PM, Noah Misch wrote:
>
> > * Identifying Parallel-Compatible Functions
> >
> > Not all functions can reasonably run on a worker backend. We should not
> > presume that a VOLATILE function can tolera
On Tue, May 14, 2013 at 11:50 AM, Noah Misch wrote:
> On Mon, May 13, 2013 at 09:52:43PM +0200, Kohei KaiGai wrote:
>> 2013/5/13 Noah Misch
>> > The choice of whether to parallelize can probably be made a manner similar
>> > to
>> > the choice to do an external sort: the planner guesses the outco
Hello,
Is it right that it is only in the case a password prompt is needed
that a new connection is created after dropping the just-failed
connection?
I created a patch which enables it to use the existing connection in
such a case (unlike what we currently do). It modifies
connectDBComplete() and
On 14.05.2013 16:48, Benedikt Grundmann wrote:
It's on the production database and the streaming replica. But not on the
snapshot.
So, the LVM snapshot didn't work correctly?
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Sometimes, the psql startup hangs when it cannot resolve or connect to a
host. Intuitively, I would like to press Ctrl+C and correct the
connection string or investigate. But that doesn't work because Ctrl+C
is already bound to the query cancel handler by that time.
It seems to me that there is
On 14.05.2013 05:34, Peter Eisentraut wrote:
In the last two years, the first commit fest started in June, which is
about a month from now. If we are going to do that again, we should
clarify that as soon as possible. And if we are not, then we should
also clarify that, because some people are
I submitted essentially this same patch over a year ago and Tom vetoed
it: http://www.postgresql.org/message-id/3741.1325731...@sss.pgh.pa.us
The thread moved to -hackers at some point and I made some further
enhancements:
http://www.postgresql.org/message-id/20120108201802.ga31...@llserver.lakel
That's one possible explanation. It's worth noting that we haven't seen
this before moving to streaming rep first and we have been using that
method for a long time.
On Tue, May 14, 2013 at 11:34 AM, Heikki Linnakangas <
hlinnakan...@vmware.com> wrote:
> On 14.05.2013 16:48, Benedikt Grundmann
PostgreSQL 9.3 Beta 1 Liberado
=
La primera versión beta de PostgreSQL 9.3, la nueva versión de la
mejor base de datos de código abierto del mundo, ahora está
disponible. Este beta
contiene vistas previas de todas las características que estarán
disponibles en la
versión 9.
2013/5/14 Jaime Casanova :
> PostgreSQL 9.3 Beta 1 Liberado
> =
>
Sorry, i was sending the announcement to a Spanish list but seems i
choose the wrong one in the email list.
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
On 14 May 2013 08:05, Simon Riggs wrote:
> I'm proposing this now as a possible GSoC project:
Unfortunately the deadline for project submissions for students was
3rd May. If this isn't worked on before next year, it can of course
be put forward as an idea for GSoC 2014.
--
Thom
--
Sent via p
On 14 May 2013 18:21, Thom Brown wrote:
> On 14 May 2013 08:05, Simon Riggs wrote:
>> I'm proposing this now as a possible GSoC project:
>
> Unfortunately the deadline for project submissions for students was
> 3rd May. If this isn't worked on before next year, it can of course
> be put forward
On 05/13/2013 08:13 PM, Peter Eisentraut wrote:
> On Mon, 2013-05-13 at 22:38 -0400, Tom Lane wrote:
>> Peter Eisentraut writes:
>>> In the last two years, the first commit fest started in June, which is
>>> about a month from now. If we are going to do that again, we should
>>> clarify that as s
Attached patch contains feature I've implemented for myself, to make
working with huge datasets easier.
I work with large datasets (1E8 - 1E9 records), and the nature of my
work is such that I must dig something out of the data on ad-hoc
basis. I spend a lot of time with psql.
Sometimes a query r
Hackers,
I'd like to add the following todo items to the TODO list:
PL/Python:
* add support for anyelement and anyarray to PL/Python
* add support for VARIADIC "ANY" to PL/Python
PL/Perl:
* add support for anyelement and anyarray to PL/Perl
* add support for VARIADIC "ANY" to PL/Perl
The reaso
> I'm proposing this now as a possible GSoC project; I don't propose to
> actively work on it myself.
The deadline for submitting GSOC projects (by students) was a week ago.
So is this a project suggestion for next year ...?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Se
On 14.05.2013 21:36, Josh Berkus wrote:
I'm proposing this now as a possible GSoC project; I don't propose to
actively work on it myself.
The deadline for submitting GSOC projects (by students) was a week ago.
So is this a project suggestion for next year ...?
I've been thinking, we shou
In the first CF for 9.4 I plan to submit a patch to allow
transactional REFRESH of a materialized view using differential
update. Essentially I expect this to be the equivalent of running
the query specified for the view and saving the results into a
temporary table, and then doing DELETE and INSE
On 14 May 2013 19:47, Heikki Linnakangas wrote:
> On 14.05.2013 21:36, Josh Berkus wrote:
>>
>>
>>> I'm proposing this now as a possible GSoC project; I don't propose to
>>> actively work on it myself.
>>
>>
>> The deadline for submitting GSOC projects (by students) was a week ago.
>> So is this
On Tue, May 14, 2013 at 11:47 AM, Heikki Linnakangas
wrote:
> I've been thinking, we should already start collecting ideas for next year,
> and collect them throughout the year. I know I come up with some ideas every
> now and then, but when it's time for another GSoC, I can't remember any of
> th
Hello
we like to use psql in combination with bash - just like postgresql driver.
Actually there is no simple possibility (from command line) to set
application_name. We would to use different name than psql - for
example "splunk", ...
I tested PGAPPNAME, but it doesn't work.
so my propose:
1
On 14 May 2013 19:51, Kevin Grittner wrote:
> In the first CF for 9.4 I plan to submit a patch to allow
> transactional REFRESH of a materialized view using differential
> update. Essentially I expect this to be the equivalent of running
> the query specified for the view and saving the results i
On 14 May 2013 20:04, Peter Geoghegan wrote:
> On Tue, May 14, 2013 at 11:47 AM, Heikki Linnakangas
> wrote:
>> I've been thinking, we should already start collecting ideas for next year,
>> and collect them throughout the year. I know I come up with some ideas every
>> now and then, but when it'
On 5/14/13 9:42 AM, Amit Kapila wrote:
In the attached patch, bgwriter/checkpointer moves unused (usage_count
=0 && refcount = 0) buffer’s to end of freelist. I have implemented a
new API StrategyMoveBufferToFreeListEnd() to
There's a comment in the new function:
It is possible that we are tol
On Tue, May 14, 2013 21:04, Pavel Stehule wrote:
> Hello
>
> we like to use psql in combination with bash - just like postgresql driver.
>
> Actually there is no simple possibility (from command line) to set
> application_name. We would to use different name than psql - for
> example "splunk", ...
2013/5/14 Erik Rijkers :
> On Tue, May 14, 2013 21:04, Pavel Stehule wrote:
>> Hello
>>
>> we like to use psql in combination with bash - just like postgresql driver.
>>
>> Actually there is no simple possibility (from command line) to set
>> application_name. We would to use different name than ps
On Tue, May 14, 2013 at 9:25 PM, Pavel Stehule wrote:
> 2013/5/14 Erik Rijkers :
>> On Tue, May 14, 2013 21:04, Pavel Stehule wrote:
>>> Hello
>>>
>>> we like to use psql in combination with bash - just like postgresql driver.
>>>
>>> Actually there is no simple possibility (from command line) to
2013/5/14 Magnus Hagander :
> psql in "connection string mode"
Hi Magnus, can me send some link?
Thank you
Pavel
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, May 14, 2013 at 9:36 PM, Pavel Stehule wrote:
> 2013/5/14 Magnus Hagander :
>> psql in "connection string mode"
>
> Hi Magnus, can me send some link?
http://www.postgresql.org/docs/9.2/static/app-psql.html
"If this parameter contains an = sign or starts with a valid URI
prefix (postgresq
2013/5/14 Magnus Hagander :
> On Tue, May 14, 2013 at 9:36 PM, Pavel Stehule
> wrote:
>> 2013/5/14 Magnus Hagander :
>>> psql in "connection string mode"
>>
>> Hi Magnus, can me send some link?
>
> http://www.postgresql.org/docs/9.2/static/app-psql.html
>
> "If this parameter contains an = sign o
On Tue, May 14, 2013 at 2:59 PM, Peter Eisentraut wrote:
>> Perhaps, but fixing the extensions is not a solution at this point. A
>> large number of extensions use this exact code (it comes from David
>> Wheeler's template AFAIK).
>
> So far, the number is still less than the number of extensions
In surveying the literature on $subject, I find that most of the
theoretical work related to how to incrementally update
materialized views based on the matview declaration was published
between 1988 and 1993. The best paper I have been able to find on
the topic was published in ACM SIGMOD in 1993
2013/5/14 Thom Brown :
> On 14 May 2013 19:51, Kevin Grittner wrote:
>> In the first CF for 9.4 I plan to submit a patch to allow
>> transactional REFRESH of a materialized view using differential
>> update. Essentially I expect this to be the equivalent of running
>> the query specified for the
On 14 May 2013 20:55, Pavel Stehule wrote:
> 2013/5/14 Thom Brown :
>> On 14 May 2013 19:51, Kevin Grittner wrote:
>>> In the first CF for 9.4 I plan to submit a patch to allow
>>> transactional REFRESH of a materialized view using differential
>>> update. Essentially I expect this to be the equ
Thom Brown wrote:
> On 14 May 2013 19:51, Kevin Grittner wrote:
>> In the first CF for 9.4 I plan to submit a patch to allow
>> transactional REFRESH of a materialized view using differential
>> update. Essentially I expect this to be the equivalent of running
>> the query specified for the view
On 14 May 2013 21:04, Kevin Grittner wrote:
> Thom Brown wrote:
>> On 14 May 2013 19:51, Kevin Grittner wrote:
>>> In the first CF for 9.4 I plan to submit a patch to allow
>>> transactional REFRESH of a materialized view using differential
>>> update. Essentially I expect this to be the equiva
On Mon, May 13, 2013 at 11:13 PM, Peter Eisentraut wrote:
> On Mon, 2013-05-13 at 22:38 -0400, Tom Lane wrote:
>> Peter Eisentraut writes:
>> > In the last two years, the first commit fest started in June, which is
>> > about a month from now. If we are going to do that again, we should
>> > cla
I think my previous message wasn't clear enough. I do *NOT* think that LVM
snapshot is the culprit.
However I cannot discount it as one of the possibilities. But I have no
evidence in either /var/log/messages or in dmesg that the LVM snapshot went
into a bad state AND we have been using this met
Marti Raudsepp writes:
> I did a quick and dirty survey of extensions on PGXN and found that
> the install change causes problems for (at least) 22% of extensions
> there. I think it's well worth the time to implement a workaround,
> rather than hassle extension writers.
What's really worrying me
On Tue, May 14, 2013 at 11:59 PM, Noah Misch wrote:
> On Tue, May 14, 2013 at 01:51:42PM +0900, Michael Paquier wrote:
> > On Mon, May 13, 2013 at 11:28 PM, Noah Misch wrote:
> >
> > > * Identifying Parallel-Compatible Functions
> > >
> > > Not all functions can reasonably run on a worker backen
On 24/02/13 10:51, Mark Kirkwood wrote:
On 24/02/13 10:12, Stefan Andreatta wrote:
On 02/23/2013 09:30 PM, Jeff Janes wrote:
Moved discussion from General To Hackers.
On Sat, Feb 23, 2013 at 10:41 AM, Stefan Andreatta
mailto:s.andrea...@synedra.com>> wrote:
On 02/23/2013 05:10 PM, Jeff
Hello,
Since, as of 9.3, there are significant changes related to shared
memory, should we change the description in
src/backend/port/sysv_shmem.c which is currently following:
*-
*
* sysv_shmem.c
*Implement shared
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> I still think we should revert 9db7ccae2000524b72a4052352cbb5407fb53b02.
> The argument that the system-provided program might be faster carries
> very little weight for me --- "make install" is fast enough already.
> It's not worth making a bunch of extensi
On Mon, May 13, 2013 at 9:54 PM, Jon Nelson wrote:
> Pertinent to another thread titled
> [HACKERS] corrupt pages detected by enabling checksums
> I hope to explore the possibility of using fallocate (or
> posix_fallocate) for new WAL file creation.
>
> Most modern Linux filesystems support fast f
On Wednesday, May 15, 2013 12:44 AM Greg Smith wrote:
> On 5/14/13 9:42 AM, Amit Kapila wrote:
> > In the attached patch, bgwriter/checkpointer moves unused
> (usage_count
> > =0 && refcount = 0) buffer's to end of freelist. I have implemented a
> > new API StrategyMoveBufferToFreeListEnd() to
>
>
On 05/13/2013 07:10 PM, Robert Haas wrote:
> On Mon, May 13, 2013 at 10:57 AM, Tom Lane wrote:
>> This approach seems to me to be likely to guarantee that the startup
>> overhead for any parallel sort is so large that only fantastically
>> enormous sorts will come out ahead.
>>
>> I think you need
Hannu Krosing writes:
> Has anybody looked into making syscache MVCC compliant ?
This is the wrong statement of the question.
The right statement is "how would you like backend A to be updating
table T in compliance with a view of table T's schema that is obsolete
because of backend B's already-
On 05/15/2013 07:30 AM, Tom Lane wrote:
> Hannu Krosing writes:
>> Has anybody looked into making syscache MVCC compliant ?
> This is the wrong statement of the question.
>
> The right statement is "how would you like backend A to be updating
> table T in compliance with a view of table T's schema
On Tuesday, May 14, 2013 7:19 PM Benedikt Grundmann wrote:
>It's on the production database and the streaming replica. But not on the
snapshot.
> production
> -rw--- 1 postgres postgres 312778752 May 13 21:28
/database/postgres/base/16416/291498116.3
> streaming replica
> -rw--- 1 postgr
On 14.05.2013 23:47, Benedikt Grundmann wrote:
The only thing that is *new* is that we took the snapshot from the
streaming replica. So again my best guess as of now is that if the
database crashes while it is in streaming standby a invalid disk state can
result during during the following start
The newly activated "make check-world" on Debian (I haven't found the
time yet to follow up on the other threads I opened for that, sorry)
actually found something: plperl and plperlu segfault on the
kfreebsd-amd64 and kfreebsd-i386 architectures. These are FreeBSD 9
kernels with a GNU/Debian userl
On Monday, May 13, 2013 7:59 PM Noah Misch wrote:
> It would be great if one client session could take advantage of
> multiple CPU
> cores. EnterpriseDB wishes to start the trek into this problem space
> for 9.4
> by implementing parallel internal (i.e. not spilling to disk) sort.
> This
> touches
79 matches
Mail list logo
