i_triggers.o' failed
When building the documentation I got two warnings:
/usr/bin/osx:catalogs.sgml:2349:17:W: empty end-tag
/usr/bin/osx:catalogs.sgml:2350:17:W: empty end-tag
When running the tests I got a failure in element_foreign_key.
Andreas
--
Sent via pgsql-hackers mailing l
:
- sslinfo
- pgcrypto
- Documentation
- Decide if what I did with the config is a good idea
Andreas
diff --git a/configure b/configure
index 4ecd2e1922..1ba34dfced 100755
--- a/configure
+++ b/configure
@@ -709,6 +709,7 @@ UUID_EXTRA_OBJS
with_uuid
with_systemd
with_selinux
+with_gnutls
with_openssl
Here is a rebased version of the patch.
Andreas
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index a0ca2851e5..f8c59ea127 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -926,6 +926,7 @@ ERROR: could not serialize access due to read/write dependencies among
case
https://git.postgresql.org/gitweb/?p=postgresql.git;a=summary should not
advertise supporting the git protocol. I have not seen any announcement
either, but that could just be me not paying enough attention.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
gml/ref/create_table.sgml which starts with
"In case the column name" seems to actually be multiple paragraphs. Is
that intentional or a mistake?
The documentation in doc/src/sgml/ddl.sgml mentions that "it must be
written in table constraint form" for when you have m
tion than adding a blacklisting/whitelisting feature and let the
user do the hard work…
If these are solved though, one could make multiple runs with the same
random seed and query the logging database for differences in the result
descriptions.
regards,
Andreas
--
Sent via pgsql-hackers mailing
EXISTS (
select
public.road.name as c1,
ref_1.with_check as c3,
ref_2.b as c6
from
public.itest4 as ref_2));
--8<---cut here---end--->8---
Backtrace below.
regards,
Andre
aintained then: https://github.com/anse1/sqlsmith. I am
> adding as well Andreas in CC, he works on sqlsmith.
Blacklisting when testing with sqlsmith typically happens on the error
logging side: Logging into a database via --log-to with the schema
shipped with sqlsmith filters out boring error mes
På onsdag 04. oktober 2017 kl. 00:24:19, skrev Vik Fearing <
vik.fear...@2ndquadrant.com <mailto:vik.fear...@2ndquadrant.com>>:
On 10/03/2017 10:10 PM, Andreas Joseph Krogh wrote:
> While we're in deferrable constraints land...;
> I even more often need deferrable /cond
rted:
CREATE UNIQUE INDEX some_uk ON email_folder(owner_id, folder_type, name) WHERE
parent_idIS NULL DEFERRABLE INITIALLY DEFERRED;
Are there any plans to support this?
Thanks.
--
Andreas Joseph Krogh
one earlier.
regards,
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Tom Lane writes:
> Presumably somebody could dig into the libc source code and prove or
> disprove this, though it would sure help to know exactly what platform
> and version Andreas is testing on.
This is the code in glibc-2.24 around the crash site:
,[ glibc-2.24/elf/dl-l
Hi,
doing low-memory testing with REL_10_STABLE at 1f19550a87 also produced
a couple of parallel worker core dumps with the backtrace below.
Although most of the backtrace is inside the dynamic linker, it looks
like it was passed a pointer to gone-away shared memory.
regards,
Andreas
Core was
e, so maybe that's
a bad idea?
regards,
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
you say in this?
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ocumentation. Does it return a BCP 47 tag in modern versions of ICU?
I strongly prefer if there, as much as possible, is only one format for
inputting ICU locales.
1.
http://www.icu-project.org/apiref/icu4c/uloc_8h.html#aa45d6457f72867880f079e27a63c6fcb
Andreas
--
Sent via
sion of ICU (or the
migration from older versions) I am all for it.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
x errors. The issue though is that we do
not want to break people's databases when they upgrade to PostgreSQL 11.
What if they have specified the locale in the old non-ICU format or they
have a bogus value and we then error out on pg_upgrade or pg_restore?
Andreas
--
Sent via pgsql-hackers m
På mandag 18. september 2017 kl. 16:28:07, skrev Bruce Momjian mailto:br...@momjian.us>>:
On Sat, Sep 16, 2017 at 11:36:40PM +0200, Andreas Joseph Krogh wrote:
> På lørdag 16. september 2017 kl. 18:34:51, skrev Bruce Momjian <
> br...@momjian.us>:
> No. If you ran in
bably has
tools for wrapping paragraphs.
Please be consistent about how you write table names and SQL in general.
I think almost all places use lower case for table names, while your
examples in create_table.sgml are FKTABLEFORARRAY.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
nuTLS versions >= 2.11.
I just very quickly fixed the broken SSL tests, as I am no fan of how
the SSL tests currently are written and think they should be cleaned up.
Andreas
diff --git a/configure b/configure
index 0d76e5ea42..33b1f00bff 100755
--- a/configure
+++ b/configure
@@ -709,
On 09/14/2017 08:33 PM, Jeff Janes wrote:> Attached is a new patch which
fixes the style issue you mentioned.
Thanks, the patch looks good no,w and as far as I can tell there was no
need to update the comments or the documentation so I am setting this as
ready for committer.
Andr
På lørdag 16. september 2017 kl. 18:34:51, skrev Bruce Momjian mailto:br...@momjian.us>>:
On Sat, Sep 16, 2017 at 06:11:17PM +0200, Andreas Joseph Krogh wrote:
> I'm a little unsure what scenario we're trying to describe here. Copying the
> pg_wal separately (for which ther
På lørdag 16. september 2017 kl. 17:24:14, skrev Bruce Momjian mailto:br...@momjian.us>>:
On Fri, Sep 15, 2017 at 01:23:45AM +0200, Andreas Joseph Krogh wrote:
> I tested upgrading from 9.6 to 10 now, using pg_upgrade, and pg_upgrade
creates
> the new data-dir with pg_wal "
På torsdag 14. september 2017 kl. 21:13:56, skrev Bruce Momjian <
br...@momjian.us <mailto:br...@momjian.us>>:
On Thu, Sep 14, 2017 at 08:49:24PM +0200, Andreas Joseph Krogh wrote:
> I think the tablespace example is clear enough to modify for WAL and we
> instruct the
På torsdag 14. september 2017 kl. 20:39:34, skrev Bruce Momjian <
br...@momjian.us <mailto:br...@momjian.us>>:
On Wed, Sep 13, 2017 at 04:31:09PM +0200, Andreas Joseph Krogh wrote:
> På onsdag 13. september 2017 kl. 15:26:27, skrev Bruce Momjian <
> br...@momjian.us>:
På onsdag 13. september 2017 kl. 15:26:27, skrev Bruce Momjian mailto:br...@momjian.us>>:
On Wed, Sep 13, 2017 at 01:35:17AM +0200, Andreas Joseph Krogh wrote:
[snip]
> I know I'm being a little nitty-gritty here, but if it helps me understand
it
> might help others.
I
s would be surprised if one can index STORED columns and
expressions but not VIRTUAL columns. So unless it is a huge project I
would say it is worth it.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
På onsdag 13. september 2017 kl. 01:54:15, skrev Stephen Frost <
sfr...@snowman.net <mailto:sfr...@snowman.net>>:
Andreas,
* Andreas Joseph Krogh (andr...@visena.com) wrote:
> I have to ask; Why not run pg_upgrade on standby, after verifying that it's
in
> sync with p
PG to realize they should do.
Thanks!
Stephen
Thanks for th explaination.
I have to ask; Why not run pg_upgrade on standby, after verifying that it's in
sync with primary and promoting it to primary if necessary and then making it
standby again after pg_upgrade is finished
På onsdag 13. september 2017 kl. 01:00:20, skrev Bruce Momjian mailto:br...@momjian.us>>:
On Wed, Sep 13, 2017 at 12:40:32AM +0200, Andreas Joseph Krogh wrote:
> På tirsdag 12. september 2017 kl. 23:52:02, skrev Bruce Momjian <
> br...@momjian.us>:
>
> On Tue, Se
På tirsdag 12. september 2017 kl. 23:52:02, skrev Bruce Momjian <
br...@momjian.us <mailto:br...@momjian.us>>:
On Tue, Sep 12, 2017 at 08:59:05PM +0200, Andreas Joseph Krogh wrote:
> Improvements?
>
> Thanks, that certainly improves things.
> But; I still fin
På tirsdag 12. september 2017 kl. 21:11:45, skrev Robert Haas <
robertmh...@gmail.com <mailto:robertmh...@gmail.com>>:
On Tue, Sep 12, 2017 at 2:59 PM, Andreas Joseph Krogh
wrote:
> There are many ways to do/configure things it seems, resulting in many ifs
> and buts whic
På tirsdag 12. september 2017 kl. 19:19:22, skrev Bruce Momjian <
br...@momjian.us <mailto:br...@momjian.us>>:
On Thu, Aug 3, 2017 at 11:37:32AM +0200, Michael Paquier wrote:
> On Mon, Jul 31, 2017 at 6:13 PM, Robert Haas wrote:
> > On Fri, Jul 28, 2017 at 10:35 AM,
should be used as a complimentary tool until the
community deems it to be good enough.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
return;
if (superuser_arg(user->userid))
return;
was, for consistency with the if clause in connect_pg_server(), written as
/* no check required if superuser */
if (superuser() || superuser_arg(user->userid))
return;
Andreas
--
l try this.
Daniel: What options does Secure Transport need for configuring ciphers,
ECDH, and cipher preference? Does it need any extra options (I think I
saw something about the keychain)?
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your su
that case;
"If upgrading from a 9.4 server or later, and you don't use Large Objects,
external utilities using logical decoding, such as pglogical or
proprietary alternatives, can also provide an alternate route,
often with lower downtime."
pg_upgrade or pg_dump is really the only option for us using LOs.
-- Andreas Joseph Krogh
hee two tests should just be removed but maybe I am
missing something.
Notes:
1. https://gnutls.org/manual/html_node/Priority-Strings.html
Andreas
diff --git a/configure b/configure
index a2f9a256b4..8dcb26b532 100755
--- a/configure
+++ b/configure
@@ -709,6 +709,7 @@ UUID_EXTRA_OBJS
with
under some
workloads, and you can still reindex each index separately if you need to.
Andreas
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index dda0170886..c97944b2c9 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -926,7 +926,7 @@ ERROR: could not seri
Tom Lane writes:
> I wonder if Andreas would be interested in trying the randomly-timed-
> SIGTERM thing with sqlsmith.
So far, most of the core dumps generated are Jeevan's assertion failing
with backtraces through SearchCatCacheList. The rest is failing this
assertion
Tom Lane writes:
> I wonder if Andreas would be interested in trying the randomly-timed-
> SIGTERM thing with sqlsmith.
Will do. Won't miss this chance to try out discostu's extension
pg_rage_terminator[1] :-)
regards,
Andreas
Footnotes:
[1] https://github.com/disco-stu/pg
y
file is less necessary for PostgreSQL than for a web server since it is
less common to do round robin load balancing between different
PostgreSQL instances.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ed, and step 10-f should
provide a clarer example with more detailed values for the directory-structures
involved.
I really think section 10 needs improvement as I'm certainly not comfortable
upgrading standbys following the existing procedure.
Thanks.
--
Andreas Joseph Krogh
ns?
Or is that too non-obvious?
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.pdf
PG is not on top wrt. CTE, but could have been if CTEs were not this
"established" fence.
+1 for removing this fence and get all the possible optimization we can.
--
Andreas Joseph Krogh
.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ption 1. And while I would not like if we had to combine it with
a backwards compatibility GUC which enables the old behavior to get it
merged I still personally would prefer that over option 2 and 3.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
On 05/02/2017 04:38 AM, Craig Ringer wrote:
On 1 May 2017 at 22:26, Andreas Karlsson wrote:
I am not sure I like decorators since this means adding an ad hoc query hint
directly into the SQL syntax which is something which I requires serious
consideration.
And mangling the semantics of
On 05/01/2017 04:33 PM, David G. Johnston wrote:
> On Mon, May 1, 2017 at 7:26 AM, Andreas Karlsson I am not sure I like decorators since this means adding an ad hoc
> query hint directly into the SQL syntax which is something which I
> requires serious consideration.
>
&
SQL terminology
"materialized subquery"?
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
is the author.
+
+
+
+Create a linkend="catalog-pg-sequence">pg_sequence system
catalog to store sequence metadata (Andreas
+Karlsson)
+
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/m
On 04/15/2017 03:58 PM, Andrew Dunstan wrote:
The instructions on how to create a self-signed certificate in s 18.9.3
of the docs seem unduly cumbersome.
+1, I see no reason for us to spread unnecessarily complicated instructions.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql
fewer
different versions of our OpenSSL code.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
g of these functions yet, so am not sure how
they best would be fixed but maybe setup_conversion could be converted
into bki entries to speed it up.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mail
ow-hanging fruit for testing speedups.
Yeah, I also noticed that the genbki code seems to have gotten little
love and that much more can be done here.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
On 04/12/2017 05:00 PM, Andreas Karlsson wrote:
Looked at this an option 1 seems simple enough if I am not missing
something. I might hack something up later tonight. Either way I think
this improvement can be done separately from the proposed replacement of
the catalog header files. Trying to
her way I think
this improvement can be done separately from the proposed replacement of
the catalog header files. Trying to fix everything at once often leads
to nothing being fixed at all.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
7;ll just put this
> in the archives for possible future reference.
>
> (Or perhaps Andreas would like to try bashing on a copy with this
> installed.)
I certainly do :-). SQLsmith has been fuzzing for couple hours with the
patch applied, and so far none of the assertions fired. I'l
Hi,
I see the above ERROR logged a lot when testing master at eef8c0069e
with a postgres_fdw around. Below is a recipe to reproduce it on top of
the regression DB.
regards,
Andreas
create extension postgres_fdw;
create server myself foreign data wrapper postgres_fdw;
create schema fdw_postgres
Hi,
testing master at f0e44021df with a loopback postgres_fdw installed, I
see lots of crashes on queries joining foreign tables with various
expressions. Below is a reduced recipe for the regression database and
a backtrace.
regards,
Andreas
--8<---cut here---st
On 04/03/2017 07:57 AM, Michael Paquier wrote:
On Fri, Mar 31, 2017 at 5:12 PM, Andreas Karlsson wrote:
On 03/31/2017 08:27 AM, Michael Paquier wrote:
- Do a per-index rebuild and not a per-relation rebuild for concurrent
indexing. Doing a per-relation reindex has the disadvantage that many
Andreas Seltenreich writes:
>>> TRAP: FailedAssertion("!(LWLockHeldByMe(((LWLock*)
>>> (&(bufHdr)->content_lock", File: "bufmgr.c", Line: 3397)
> I got about one TRAP per hour when testing on 20 nodes with one postgres
> and 5 s
between temporary disk usage and time
spent waiting for transactions, and doing the REINDEX per relation
allows for flexibility since people can still explicitly reindex per
index of they want to.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
nt. Otherwise I have to be creative myself writing
commit messages in order to keep track of which patches are applied on
the branch sqlsmith is crunching on.
regards,
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.po
mand:
"/home/andreas/dev/postgresql/src/bin/pg_upgrade/tmp_check/install//home/andreas/dev/postgresql-inst/bin/pg_dump"
--host /home/andreas/dev/postgresql/src/bin/pg_upgrade --port 50848
--username andreas --schema-only --quote-all-identifiers
--binary-upgrade --format=custom --file="
et this crash.
I got about one TRAP per hour when testing on 20 nodes with one postgres
and 5 sqlsmithes on each. Nodes are tiny consumer machines with
low-power 4-core sandy bridges.
> [2. reacquire_lock_hashkillitems_if_required.patch]
I'll test with your patch applied as soon as time
On 03/27/2017 04:38 PM, Peter Eisentraut wrote:
Committed.
Thanks!
While digging around a bit, I found in release-old.sgml that before
PostgreSQL 7.2, pg_clog was called pg_log. Go figure.
Yeah, I noticed that too when writing the patch. :)
Andreas
--
Sent via pgsql-hackers mailing
d be left there.
It should be directly after g_verbose.
- There is something wrong with the indentation of the query for
collecting info about databases in dumpDatabase() for PG >= 9.6.
- Missing space before "'' as rdatacl" in dumpDatabase(), and a missing
space at t
or in their logfiles:
FATAL: cannot unpin a segment that is not pinned
Below are the backtraces of the processes throwing them.
regards,
Andreas
Backtrace on dwagon:
#0 sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
#1 0x006b7c02 in PGSemaphoreLock (sema=0x7
ucible on a
cluster once it happens. I could provide a tarball if needed.
regards,
Andreas
#2 0x008324b1 in ExceptionalCondition
(conditionName=conditionName@entry=0x9e4e28 "!(LWLockHeldByMe(((LWLock*)
(&(bufHdr)->content_lock", errorType=errorType@entry=0x87b03d
eventually be able to
drop their LD_PRELOAD hack, which never worked perfectly due to
compiling against libedit or libreadline header resulting in different
binaries.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
rong
preference other than that we should avoid breaking pg_dump or changing
behavior not related to the database attributes.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
nk we will just have to accept the weirdness of how ICU handles
locales.
I think this patch is ready to be committed.
Found a typo in the documentation:
"The inspect the currently available locales" should be "To inspect the
currently available locales".
Andreas
not a problem since we don't
-* support adding any-encoding entries after initdb.
+* support adding any-encoding entries after initdb. FIXME
*/
I had mentioned that upthread. It technically needs "doing" as you say,
but it's not clear how and it's not terribly important, arguably.
The comment is no longer true since for ICU we can do that (it is not an
issue though). At the very least this comment needs to be updated.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
upgrade. On the flip side I have no idea
how much work it would be to maintain those legacy names.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
I'd suggest dropping these too.
The value they add is that they quote the database name and options
correctly which makes them easier to use safely and reliably in shell
scripts. And unless I am missing something obvious I do not think there
is any easy way for a beginner to do this
On 03/17/2017 12:01 AM, Peter Eisentraut wrote:
Committed with some tweaking.
Thanks!
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ater.
After further discussion, Peter will propose another solution soon.
--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project
--
Sent via pgs
Hi,
I got a test failure with this version of the patch in the postges_fdw.
It looks to me like it was caused by a typo in the source code which is
fixed in the attached patch.
After applying this patch check-world passes.
Andreas
diff --git a/src/backend/executor/nodeTidscan.c b/src
On 03/01/2017 02:47 PM, Peter Eisentraut wrote:
Instead of creating another copy of list_ALTER, let's use the
words_after_create list and write a version of
create_command_generator/drop_command_generator.
Good idea. Here is a patch with that.
Andreas
c
ill needs doing?
/*
* Also forbid matching an any-encoding entry. This test of course
is not
* backed up by the unique index, but it's not a problem since we don't
-* support adding any-encoding entries after initdb.
+* support adding any-encoding entries after initdb. FIXME
*/
- Should functions like normalize_locale_name() be renamed to indicate
they relate to libc locales? I am leaning towards doing so but have not
looked closely at the task.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 03/13/2017 03:56 PM, David Steele wrote:
Do you know when you will have a new patch available for review that
incorporates Peter's request?
I believe I will find the time to finish it some time in a couple of days.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-ha
On 03/13/2017 03:11 AM, Andreas Karlsson wrote:
I also fixed the the code to properly support triggers.
And by "support triggers" I actually meant fixing the support for moving
the foreign keys to the new index.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@post
On 03/02/2017 03:10 AM, Michael Paquier wrote:
On Wed, Mar 1, 2017 at 2:21 AM, Andreas Karlsson wrote:
+/*
+ * Copy contraint flags for old index. This is safe because the old index
+ * guaranteed uniquness.
+ */
+newIndexForm->indisprimary = oldIndexForm->indisp
På fredag 10. mars 2017 kl. 10:34:48, skrev Rushabh Lathia <
rushabh.lat...@gmail.com <mailto:rushabh.lat...@gmail.com>>:
On Fri, Mar 10, 2017 at 2:42 PM, Andreas Joseph Krogh mailto:andr...@visena.com>> wrote: På fredag 10. mars 2017 kl. 10:09:22, skrev
Rushabh Lathia
hile developing. Fun little tidbit there.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
På fredag 10. mars 2017 kl. 10:09:22, skrev Rushabh Lathia <
rushabh.lat...@gmail.com <mailto:rushabh.lat...@gmail.com>>:
On Fri, Mar 10, 2017 at 2:33 PM, Andreas Joseph Krogh mailto:andr...@visena.com>> wrote: [...]
The execution-plan seems (unsurprisingly) to depend on
På fredag 10. mars 2017 kl. 09:53:47, skrev Rushabh Lathia <
rushabh.lat...@gmail.com <mailto:rushabh.lat...@gmail.com>>:
On Fri, Mar 10, 2017 at 1:44 PM, Andreas Joseph Krogh mailto:andr...@visena.com>> wrote: På torsdag 09. mars 2017 kl. 18:09:45,
skrev Robert Ha
│
│ Execution time: 170.859 ms
│
-- Andreas Joseph Krogh
On 03/07/2017 09:56 PM, Sven R. Kunze wrote:
On 07.03.2017 03:21, Andreas Karlsson wrote:
1) I do not think we currently allow setting the locale like this
anywhere, so this will introduce a new concept to PostgreSQL. And you
will probably need to add support for caching per locale.
Good to
On 03/08/2017 03:48 AM, Robert Haas wrote:
On Sun, Mar 5, 2017 at 7:13 PM, Andreas Karlsson wrote:
And I would argue that his feature is useful for quite many, based on my
experience running a semi-large database. Index bloat happens and without
REINDEX CONCURRENTLY it can be really annoying
pissing too many
users off, but I have no idea if this is a view shared with the rest of
the community.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Btw, is there a reason for why global and base do not have the "pg_" prefix?
Andreas
commit 0b71fcdb328f05349775675e0491ba1b82127d4e
Author: Andreas Karlsson
Date: Mon Mar 6 23:52:49 2017 +0100
Rename default log directory from pg_log to log
diff --git a/doc/src/sgml/config.sgml b/d
/var/log, and if you
unpack a, say, Kafka or Cassandra distribution, they also come with a
log or logs directory.
+1, though I am also fine with server_log.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
tabase. Index bloat happens and
without REINDEX CONCURRENTLY it can be really annoying to solve,
especially for primary keys. Certainly more people have problems with
index bloat than the number of people who store index oids in their
database.
Andreas
--
Sent via pgsql-hackers mailing lis
On 03/02/2017 02:25 AM, Jim Nasby wrote:
On 2/28/17 11:21 AM, Andreas Karlsson wrote:
The only downside I can see to this approach is that we no logner will
able to reindex catalog tables concurrently, but in return it should be
easier to confirm that this approach can be made work.
Another
ns we change each index from
invalid to dead.
6. After waiting for all running transactions we drop each index.
7. Drop all session locks.
Andreas
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index 306def4a15..ca1aeca65f 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src
4 Protocol section or removed?
A new protocol version wont solve the breakage of the C API, so I am not
sure we can ever drop this feature other than by adding a new function
something in the protocol to support this.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgres
memory context
be removed, or should we switch to TopTransactionContext at the begining
of ReindexMultipleTables() so temporary resources used in the initial
transaction can be freed?
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
1 - 100 of 2250 matches
Mail list logo
