On Tue, Aug 30, 2016 at 6:38 PM, Tom Lane wrote:
> Kyotaro HORIGUCHI writes:
>> - boolsingle_copy;/* path must not be executed >1x */
>> + boolsingle_copy;/* path must not span on multiple
>> processes */
>
> I agree that the existing comment sucks, but th
On Wed, Aug 31, 2016 at 2:15 AM, Tom Lane wrote:
> Michael Paquier writes:
>> And with an actual patch things are better.
>
> Working through this patch, it suddenly strikes me that we are going
> about fixing the callers of simple_prompt the wrong way. The existing
> definition with returning a
2016-08-31 8:17 GMT+02:00 Jeevan Chalke :
>
>
> On Tue, Aug 30, 2016 at 6:51 PM, Pavel Stehule
> wrote:
>
>> Hi
>>
>> 2016-08-30 15:02 GMT+02:00 Jeevan Chalke
>> :
>>
>>> Hi all,
>>>
>>> Attached is the patch which adds support to push down aggregation and
>>> grouping
>>> to the foreign server
On Tue, Aug 30, 2016 at 6:51 PM, Pavel Stehule
wrote:
> Hi
>
> 2016-08-30 15:02 GMT+02:00 Jeevan Chalke :
>
>> Hi all,
>>
>> Attached is the patch which adds support to push down aggregation and
>> grouping
>> to the foreign server for postgres_fdw. Performing aggregation on foreign
>> server res
On 30 August 2016 at 20:50, Peter Eisentraut
wrote:
>
> - Patches to PL/pgSQL to implement Oracle-style autonomous transaction
> blocks:
>
> AS $$
> DECLARE
> PRAGMA AUTONOMOUS_TRANSACTION;
> BEGIN
> FOR i IN 0..9 LOOP
> START TRANSACTION;
> INSERT INTO test1 VALUES (i);
> IF i % 2
On Tue, Aug 30, 2016 at 11:00 PM, Tom Lane wrote:
> Michael Paquier writes:
>> Does the attached suit better then?
>
> Thinking about it some more ... what we actually need to prevent, AFAICS,
> is standby_mode becoming true in a standalone backend. If you don't set
> that, then the process will
On 30 August 2016 at 23:10, Joel Jacobson wrote:
>
> There should be a way to within the session and/or txn permanently
> block autonomous transactions.
>
This will defeat one of the use cases of autonomous transactions: auditing
>
> Coding conventions, rules and discipline are all good and will
On Wed, Aug 31, 2016 at 1:12 PM, Peter Eisentraut
wrote:
> On 8/30/16 11:27 PM, Craig Ringer wrote:
>> Speaking of which, have you had a chance to try it on Windows yet?
>
> nope
+SELECT a, b FROM collate_test2 ORDER BY b;
+ a | b
+---+-
+ 1 | abc
+ 4 | ABC
+ 3 | bbc
+ 2 | äbc
+(4 rows)
Be c
Here is a patch that adds the notion of a data type to a sequence. So
it might be CREATE SEQUENCE foo AS integer. The types are restricted to
int{2,4,8} as now.
The main point of this is to make monitoring sequences less complicated.
Right now, a serial column creates an int4 column but creates
On 8/30/16 11:27 PM, Craig Ringer wrote:
> Speaking of which, have you had a chance to try it on Windows yet?
nope
> How stable are the UCU locales? Most importantly, does ICU offer any
> way to "pin" a locale version, so we can say "we want de_DE as it was
> in ICU 4.6" and get consistent behavi
I would love to see autonomous transactions in core.
I just have one major concern, but thankfully it's easily addressed.
There should be a way to within the session and/or txn permanently
block autonomous transactions.
This is important if you as a caller function want to be sure none of
the wo
Here is another attempt to implement identity columns. This is a
standard-conforming variant of PostgreSQL's serial columns. It also
fixes a few usability issues that serial columns have:
- need to set permissions on sequence in addition to table (*)
- CREATE TABLE / LIKE copies default but refe
On 31 August 2016 at 10:46, Peter Eisentraut
wrote:
> Here is a patch I've been working on to allow the use of ICU for sorting
> and other locale things.
Great to see you working on this. We've got some icky head-in-the-sand
issues in this area when it comes to OS upgrades, cross-OS-release
repli
Here is a patch I've been working on to allow the use of ICU for sorting
and other locale things.
This is mostly complementary to the existing FreeBSD ICU patch, most
recently discussed in [0]. While that patch removes the POSIX locale
use and replaces it with ICU, my interest was on allowing the
I would like to propose the attached patch implementing autonomous
transactions for discussion and review.
This work was mostly inspired by the discussion about pg_background a
while back [0]. It seemed that most people liked the idea of having
something like that, but couldn't perhaps agree on t
On Wed, Aug 31, 2016 at 2:06 AM, Alvaro Herrera
wrote:
> Jesper Pedersen wrote:
>> Attached is a patch that adds support for hash indexes in pageinspect.
>>
>> The functionality (hash_metap, hash_page_stats and hash_page_items) follows
>> the B-tree functions.
>
> I suggest that pageinspect functi
On 25 Aug. 2016 20:03, "Stas Kelvich" wrote:
>
> > On 20 Aug 2016, at 15:59, Craig Ringer wrote:
> >
> > I'll wait for a test case or some more detail.
>
> Thanks for clarification about how restart_lsn is working.
>
> Digging slightly deeper into this topic revealed that problem was in two
phase
Michael Paquier writes:
> [ malloc-nulls-v5.patch ]
I've committed some form of all of these changes except the one in
adt/pg_locale.c. I'm not entirely sure whether we need to do anything
about that at all, but if we do, this doesn't cut it:
thousands_sep = db_encoding_strdup(encoding, ex
On 2016-08-30 21:59:44 +0100, Greg Stark wrote:
> On Tue, Aug 30, 2016 at 11:12 AM, Heikki Linnakangas wrote:
> > While profiling some queries and looking at executor overhead, I realized
> > that we're not making much use of TupleTableSlot's ability to hold a buffer
> > pin. In a SeqScan, the buf
On Tue, Aug 30, 2016 at 11:12 AM, Heikki Linnakangas wrote:
> While profiling some queries and looking at executor overhead, I realized
> that we're not making much use of TupleTableSlot's ability to hold a buffer
> pin. In a SeqScan, the buffer is held pinned by the underlying heap-scan
> anyway.
On 2016-08-30 08:46:48 -0400, Peter Eisentraut wrote:
> I was toying with a couple of ideas that would involve changing the
> storage of sequences. (Say, for the sake of discussion, removing the
> problematic/useless sequence_name field.)
I'd be quite interested to know what changes that are...
Hi,
On 2016-08-30 13:12:41 +0300, Heikki Linnakangas wrote:
> While profiling some queries and looking at executor overhead, I realized
> that we're not making much use of TupleTableSlot's ability to hold a buffer
> pin.
FWIW, I came to a similar conclusion, while working on passing around
making
On 08/30/2016 02:38 PM, Tom Lane wrote:
Heikki Linnakangas writes:
While profiling some queries and looking at executor overhead, I
realized that we're not making much use of TupleTableSlot's ability to
hold a buffer pin. In a SeqScan, the buffer is held pinned by the
underlying heap-scan anywa
On 2016-08-30 11:22:43 +0300, Maksim Milyutin wrote:
> > Hi,
> >
> > On 2016-08-29 18:22:56 +0300, maksim wrote:
> > > Now I complete extension that provides facility to see the current state
> > > of
> > > query execution working on external session in form of EXPLAIN ANALYZE
> > > output. This
Haribabu Kommi wrote:
> Apart from the above, here are the following list of command tags that
> are generated in the code, I took only the first word of the command tag
> just to see how many categories present. The number indicates the
> subset of operations or number of types it is used. Like c
Michael Paquier writes:
> And with an actual patch things are better.
Working through this patch, it suddenly strikes me that we are going
about fixing the callers of simple_prompt the wrong way. The existing
definition with returning a malloc'd string creates a hazard of malloc
failure, and it
Jesper Pedersen wrote:
> Hi,
>
> Attached is a patch that adds support for hash indexes in pageinspect.
>
> The functionality (hash_metap, hash_page_stats and hash_page_items) follows
> the B-tree functions.
I suggest that pageinspect functions are more convenient to use via the
get_raw_page int
On Tue, Aug 30, 2016 at 08:46:48AM -0400, Peter Eisentraut wrote:
> I think the other solution mentioned in that thread would also work:
> Have pg_upgrade treat sequences more like system catalogs, whose format
> changes between major releases, and transferred them via the
> dump/restore route. So
Fujii Masao writes:
> I found that pg_xlogdump code for XLOG_GIN_INSERT record with
> GIN_INSERT_ISLEAF flag has the same issue, i.e.,
> "unknown action 0" error is thrown for that record.
> The latest patch fixes this.
Hmm, comparing gin_desc() to ginRedoInsert() makes me think there are more
pr
Hi,
Attached is a patch that adds support for hash indexes in pageinspect.
The functionality (hash_metap, hash_page_stats and hash_page_items)
follows the B-tree functions.
This patch will need an update once Amit's and Mithun's work on
Concurrent Hash Indexes is committed to account for the
Hi
I am working on pgaudit customization for one my customer.
There are few requests:
1. flat format without complex types, without nesting - CSV is ideal.
2. all important attributes should be separated - is not possible to search
in original queries: table name, database name, role name, right
Michael Paquier writes:
> Does the attached suit better then?
Thinking about it some more ... what we actually need to prevent, AFAICS,
is standby_mode becoming true in a standalone backend. If you don't set
that, then the process will do PITR recovery, but I'm not aware that there
is any proble
Aleksander Alekseev writes:
> I suggest to keep ShmemAlloc as is for backward compatibility and
> introduce a new procedure ShmemAllocSafe.
I think that's about the worst of all possible worlds, as it guarantees
having to touch most call sites. If there were more than one known caller
that reall
Michael Paquier writes:
> On Tue, Aug 30, 2016 at 10:18 PM, Tom Lane wrote:
>> I think what we ought to do is make ShmemAlloc act like palloc
>> (ie throw error not return NULL), and remove the duplicated error
>> checks.
> The only reason why I did not propose that for ShmemAlloc is because
> o
On Tue, Aug 30, 2016 at 10:24 PM, Tom Lane wrote:
> Michael Paquier writes:
>> On Tue, Aug 30, 2016 at 9:48 PM, Tom Lane wrote:
>>> Hm, StartupXLOG seems like a pretty random place to check that, especially
>>> since doing it there requires an extra stat() call. Why didn't you just
>>> make rea
> > I think what we ought to do is make ShmemAlloc act like palloc
> > (ie throw error not return NULL), and remove the duplicated error
> > checks. For the one caller that that would be bad for, we could
> > invent something like ShmemAllocNoError, or ShmemAllocExtended with
> > a no_error flag,
On Tue, Aug 30, 2016 at 10:18 PM, Tom Lane wrote:
> I think what we ought to do is make ShmemAlloc act like palloc
> (ie throw error not return NULL), and remove the duplicated error
> checks. For the one caller that that would be bad for, we could
> invent something like ShmemAllocNoError, or Sh
Michael Paquier writes:
> On Tue, Aug 30, 2016 at 9:48 PM, Tom Lane wrote:
>> Hm, StartupXLOG seems like a pretty random place to check that, especially
>> since doing it there requires an extra stat() call. Why didn't you just
>> make readRecoveryCommandFile() error out?
> Well, the idea is to
Hi
2016-08-30 15:02 GMT+02:00 Jeevan Chalke :
> Hi all,
>
> Attached is the patch which adds support to push down aggregation and
> grouping
> to the foreign server for postgres_fdw. Performing aggregation on foreign
> server results into fetching fewer rows from foreign side as compared to
> fet
Michael Paquier writes:
>> I've just realized that there is also malloc-compatible ShmemAlloc().
>> Apparently it's return value sometimes is not properly checked too. See
>> attachment.
> The funny part here is that ProcGlobal->allProcs is actually handled,
> but not the two others. Well yes, yo
Kyotaro HORIGUCHI writes:
> - boolsingle_copy;/* path must not be executed >1x */
> + boolsingle_copy;/* path must not span on multiple
> processes */
I agree that the existing comment sucks, but this isn't a lot better
(and it will probably not look nice
On Tue, Aug 30, 2016 at 9:48 PM, Tom Lane wrote:
> Michael Paquier writes:
>> On Wed, Aug 24, 2016 at 5:07 PM, Bernd Helmle wrote:
>>> That said, i'm okay if --single is not intended to bring up a hot standby.
>>> There are many other ways to debug such problems.
>
>> This patch is still on the
Peter Eisentraut writes:
> I was toying with a couple of ideas that would involve changing the
> storage of sequences. (Say, for the sake of discussion, removing the
> problematic/useless sequence_name field.) This would cause problems for
> pg_upgrade, because pg_upgrade copies the "heap" stora
Michael Paquier writes:
> On Wed, Aug 24, 2016 at 5:07 PM, Bernd Helmle wrote:
>> That said, i'm okay if --single is not intended to bring up a hot standby.
>> There are many other ways to debug such problems.
> This patch is still on the CF app:
> https://commitfest.postgresql.org/10/610/
> Eve
I was toying with a couple of ideas that would involve changing the
storage of sequences. (Say, for the sake of discussion, removing the
problematic/useless sequence_name field.) This would cause problems for
pg_upgrade, because pg_upgrade copies the "heap" storage of sequences
like it does for n
Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= writes:
> They wanted to change id column from uuid to int, so created this func first:
> CREATE FUNCTION foofunc_id_uuidtoint(chartoconvert uuid) RETURNS integer
> LANGUAGE sql IMMUTABLE STRICT
> AS $_$
> SELECT newid FROM foo1 WHERE tempuuid = $1 LIMIT
On Fri, Aug 26, 2016 at 1:34 PM, Peter Eisentraut
wrote:
> I doubt the documentation for old_snapshot_threshold is going to be
> understood by many ordinary users. What is a "snapshot", first of all?
> Why would a snapshot be old? Why is that a problem? What can I do to
> avoid it? What are th
"K S, Sandhya (Nokia - IN/Bangalore)" writes:
> During the server restart, we are getting postgres crash with sigabrt. No
> other operation being performed.
> Attached the backtrace.
What shows up in the postmaster log?
> The occurrence is occasional. The issue is seen once in 30~50 times.
Doe
Heikki Linnakangas writes:
> While profiling some queries and looking at executor overhead, I
> realized that we're not making much use of TupleTableSlot's ability to
> hold a buffer pin. In a SeqScan, the buffer is held pinned by the
> underlying heap-scan anyway. Same with an IndexScan, and t
Hello,
During the server restart, we are getting postgres crash with sigabrt. No other
operation being performed.
Attached the backtrace.
The occurrence is occasional. The issue is seen once in 30~50 times.
Recently we had performed postgres upgrade from 9.3.9 to 9.3.11. The issue is
not seen
While profiling some queries and looking at executor overhead, I
realized that we're not making much use of TupleTableSlot's ability to
hold a buffer pin. In a SeqScan, the buffer is held pinned by the
underlying heap-scan anyway. Same with an IndexScan, and the SampleScan.
The only thing that
On Fri, Aug 26, 2016 at 10:10 AM, Mithun Cy
wrote:
>
> >rpath,'/home/mithun/edbsrc/patch6bin/lib',--enable-new-dtags -lecpg
> -lpgtypes -lpq -lpgcommon -lpgport -lz -lrt -lcrypt -ldl -lm -o test1
> >../../../../../src/interfaces/libpq/libpq.so: undefined reference to
> `pg_usleep'
>
As similar
Hi,
I received an email offlist about a crash that a non-customer experienced
recently. I asked them to send a few details about the crash, so here it is.
Please note that I don't have access to their systems, but they will be fast
enough to provide data if needed. (They asked me to mask some of
2016-08-30 2:02 GMT-03:00 Michael Paquier :
> On Tue, Aug 30, 2016 at 5:43 AM, Martín Marqués
> wrote:
>> This is v4 of the patch, which is actually a cleaner version from the
>> v2 one Michael sent.
>>
>> I stripped off the external index created from the tests as that index
>> shouldn't be dump
Hi,
On 2016-08-29 18:22:56 +0300, maksim wrote:
Now I complete extension that provides facility to see the current state of
query execution working on external session in form of EXPLAIN ANALYZE
output. This extension works on 9.5 version, for 9.6 and later it doesn't
support detailed statistics
> >> And with an actual patch things are better.
> >
> > Currently I can't think of any further improvements. I even would dare
> > to say that patch is Ready for Committer.
>
> Thanks for the fruitful input by the way! You spotted many things.
Thank _you_ for paying attention for such issues in
On Tue, Aug 30, 2016 at 5:08 PM, Aleksander Alekseev
wrote:
>> > The funny part here is that ProcGlobal->allProcs is actually handled,
>> > but not the two others. Well yes, you are right, we really need to
>> > fail on FATAL for all of them if ShmemAlloc returns NULL as they
>> > involve the shme
> > The funny part here is that ProcGlobal->allProcs is actually handled,
> > but not the two others. Well yes, you are right, we really need to
> > fail on FATAL for all of them if ShmemAlloc returns NULL as they
> > involve the shmem initialization at postmaster startup.
>
> And with an actual p
On Tue, Aug 30, 2016 at 3:13 PM, Fujii Masao wrote:
> On Tue, Aug 30, 2016 at 3:39 AM, Tom Lane wrote:
>> Fujii Masao writes:
>>> ISTM that the cause of this issue is that gin_desc() uses XLogRecGetData()
>>> to
>>> extract ginxlogVacuumDataLeafPage data from XLOG_GIN_VACUUM_DATA_LEAF_PAGE
>>>
On Mon, Aug 29, 2016 at 5:22 PM, maksim mailto:m.milyu...@postgrespro.ru>> wrote:
Hi, hackers!
Now I complete extension that provides facility to see the current
state of query execution working on external session in form of
EXPLAIN ANALYZE output. This extension works on 9.5 ve
On 28 August 2016 at 21:23, Joe Conway wrote:
> Apologies for the delay, but new patch attached. Assuming no more
> comments, will commit this, backpatched to 9.5, in a day or two.
>
Looking at this again, I think there is something fishy about these
dump/restore flags.
If you do pg_dump --enabl
61 matches
Mail list logo
