Re: [HACKERS] [PATCH] Alter or rename enum value

feature! Given that you are now familiar with the internals of how enums are implemented would it be possible to continue the work and add the "ALTER TYPE DROP VALUE " command? Thank you! Regards, Matthias

Re: [HACKERS] Alter or rename enum value

> > It's conceivable that we could do something like adding an "isdead" > column to pg_enum and making enum_in reject new values that're marked > isdead. But I can't see that we'd ever be able to support true > removal of an enum value at reasonable cost. And I'm not really sure > where the use-c

Re: [HACKERS] Alter or rename enum value

> > ilm...@ilmari.org (Dagfinn Ilmari Mannsåker) writes: > > > > > I was bored and thought "how hard could it be?", and a few hours' > > hacking later, I have something that seems to work. It doesn't do IF > > NOT EXISTS yet, and the error messaging could do with some improvement, > > and there ar

Re: [HACKERS] Alter or rename enum value

On 9 March 2016 at 20:19, Matthias Kurz wrote: > Besides not being able to rename enum values there are two other > limitations regarding enums which would be nice to get finally fixed: > > 1) There is also no possibility to drop a value. > > 2) Quoting the docs ( > http

Re: [HACKERS] Alter or rename enum value

this changes wouldn't be that disruptive anymore? Regards, Matthias On 9 March 2016 at 18:13, Tom Lane wrote: > Andrew Dunstan writes: > > On 03/09/2016 11:07 AM, Tom Lane wrote: > >> I have a vague recollection that we discussed this at the time the enum > >>

[HACKERS] Alter or rename enum value

hanks! Greetings, Matthias

[HACKERS] Fwd: Range types (DATERANGE, TSTZRANGE) in a foreign key with "inclusion" logic

Hello, this is a re-post from the SQL user list 2 month ago, because I assume only a developer can answer the questions below. Thanks, Matthias Nagel -- Weitergeleitete Nachricht -- Betreff: Range types (DATERANGE, TSTZRANGE) in a foreign key with "inclusion" l

Re: [HACKERS] Hash Join cost estimates

any way to when I was running with the laptop connected straight to a socket. Things like IO/CPU ratio were completely different. And numbers on the final testing servers were even different. Of course your test case might not be affected by this at all, but it's something to watch out f

Re: [HACKERS] HEAD crashes on windows when doing VACUUM ANALYZE

2012/8/30 Albe Laurenz : > Matthias wrote: >> when running VACUUM ANALYZE on my database built on win32-x86 from >> yesterday's git checkout I always get this at some point during VACUUM >> ANALYZE: >> >> LOG: server process (PID 5880) was terminated by e

[HACKERS] Query plan optimization for CHECK NO INHERIT and single table?

the query plan could just do a seq/index/whatever scan on that table. Right now the query plan has an intermediate "Append" node. This seems only useful if the results of multiple child tables would need to be included. -Matthias -- Sent via pgsql-hackers mailing list (pgs

[HACKERS] HEAD crashes on windows when doing VACUUM ANALYZE

See C include file "ntstatus.h" for a description of the hexadecimal value. LOG: terminating any other active server processes I am not sure if it's useful to report it here, but I thought I'd do it anyway :) -Matthias -- Sent via pgsql-hackers mailing list (pgsql-hacker

Re: [HACKERS] Statistics and selectivity estimation for ranges

avoid problems like "the new range types are slow" (just due to the bad row estimates). Thanks for implementing this feature, -Matthias -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Fwd: Statistics and selectivity estimation for ranges

avoid problems like "the new range types are slow" (just due to the bad row estimates). Thanks for implementing this feature, -Matthias -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] XQuery support

ncy for > Zorba was ICU for converting character sets. I'm not familiar with that part > of Postgres. But it seems to me that we would have our own libraries for that > sort of thing. Please find answers to this in my previous email. Thanks & best regards, Matthias -- Sent via

Re: [HACKERS] XQuery support

dency which is used for Unicode support. Specifically, Zorba uses it for regular expression evaluation and collation support. Best regards Matthias -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] XQuery support

Please, let us know (zorba-us...@lists.sourceforge.net) if you need any help or have questions with regard to plugging Zorba to PostGreSQL. We would love to see this happen and help. Best regards, Matthias -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] --enable-debug does not work with gcc

ness for the debugging section in the Dev FAQ? Are there any other macros that enable some more debug output? (Or is there a place where all this has already been documented?) Cheers, Matthias ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [HACKERS] Where to see the patch queue (was Re: [PATCHES] Patch for Postmaster

don't have any preference which Trouble-Ticket System to use. But I think the idea of having one is worth considering. cheers, Matthias Am 25.02.2005 um 03:51 schrieb Bruce Momjian: Eric Crampton wrote: On Feb 24, 2005, at 5:38 PM, Tom Lane wrote: "Eric Crampton" <[EMAIL PROTEC

Re: [HACKERS] Allow GRANT/REVOKE permissions to be applied to all schema objects with one command

Hi Merlin, sorry - I replied to Tom & PG hackers before I saw you last post. I think it is best to code the basic functionallity within the two new commands, and see how this works out. We can add your idea and others on top of it later on. what about that? cheers, Matt

Re: [HACKERS] [pgsql-hackers] Allow GRANT/REVOKE permissions to be applied to all schema

Hi *, I will start implementing this stuff based on this syntax: GRANT SELECT ON ALL TABLES IN public TO phpuser; GRANT SELECT ON NEW TABLES IN public TO phpuser; so there are two seperate commands to use. is everybody fine with this aproach? cheers, Matthias PS.: Tom, shouldn't we mentio

Re: [HACKERS] Allow GRANT/REVOKE permissions to be applied to all schema objects with one command

this case the grant on schema's need to swallow the permissions (SELECT, INSERT, UPDATE ...) which are intended for TABLES. This seems to me kind of strange. therefore I vote for Syntax a) What do you think? cheers, Matthias Hi Tom + *, as I learned from severall posts this TODO

[HACKERS] Allow GRANT/REVOKE permissions to be applied to all schema objects with one command

. my questions are: a) should we pursue both of them? b) how can a syntax for TODO1 look like? Anchored at 'GRANT ... ON SCHEMA' or 'GRANT ... ON ' ? greetings, Matthias -- Matthias Schmidt Viehtriftstr. 49 67346 Spey

Re: [HACKERS] Some things I like to pick from the TODO list ...

OK guys - i think I go for #3: Allow GRANT/REVOKE permissions to be applied to all schema objects with one cheers, Matthias Am 18.01.2005 um 20:47 schrieb Tom Lane: Matthias Schmidt <[EMAIL PROTECTED]> writes: These are the things I'm interested in: 1) Allow limits on per-db/user co

[HACKERS] Some things I like to pick from the TODO list ...

chema objects with one 4) Allow PREPARE of cursors what's free, what's apropriate for a newbee like me? cheers, Matthias -- Matthias Schmidt Viehtriftstr. 49 67346 Speyer GERMANY Tel.: +49 6232 4867 Fax.:

Re: [HACKERS] uptime() for postmaster

Hi Tom, Am 31.12.2004 um 20:18 schrieb Tom Lane: Matthias Schmidt <[EMAIL PROTECTED]> writes: a) is the name uptime() OK? Probably should use pg_uptime(), or something else starting with pg_. What about 'pg_starttime()' since it is not a period but a point-in-time? b) is

[HACKERS] uptime() for postmaster

gy-back on 'BackendParameters' to get postmasters start-time to the backends? happy new year, Matthias ------ Matthias Schmidt Viehtriftstr. 49 67346 Speyer Tel.: +49 6232 4867 Fax.: +49 6232 640089

Re: [HACKERS] somebody working on: Prevent default re-use of sysids for dropped users and groups?

Hi Tom, after beeing offline because of a chrashed box, I able to mail again. I would like to volunteer for the uptime() function. Is that OK? cheers, Matthias Am 13.12.2004 um 03:31 schrieb Bruce Momjian: Matthias Schmidt wrote: Am 07.12.2004 um 19:24 schrieb Tom Lane: Matthias Schmidt <[EM

Re: [HACKERS] somebody working on: Prevent default re-use of sysids for dropped users and groups?

Am 07.12.2004 um 19:24 schrieb Tom Lane: Matthias Schmidt <[EMAIL PROTECTED]> writes: By the way: Do you have an idea about a small or medium sized task from the TODO-List for a newbee, which gets me up to speed?(!Win32) A lot of the tasks listed under DATA TYPES are fairly self-contained pr

Re: [HACKERS] somebody working on: Prevent default re-use of sysids for dropped users and groups?

a good starting point, but I cannot figure out who works on what. cheers, Matthias -- Matthias Schmidt Viehtriftstr. 49 67346 Speyer Tel.: +49 6232 4867 Fax.: +49 6232 640089 ---(end of broadcast)---

[HACKERS] UB-Trees

://mistral.in.tum.de/index.html Thanks for any information! Ciao! Matthias ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html

[HACKERS] CVS tags for betas and release candidate

Hi there. I was just looking for the CVS tags for downloading the beta6 and the RC1 of 7.1 but there are only the following tags: REL_7_1_BETA2 REL_7_1_BETA3 REL_7_1 Aren't there tags for the versions I am looking for? Regards, Matthias ---(end of broa

[HACKERS] regression test result HP-UX 11.00, PA8500

contact me. Regards, Matthias *** ./expected/geometry-positive-zeros.out Tue Sep 12 23:07:16 2000 --- ./results/geometry.out Tue Mar 27 01:23:47 2001 *** *** 114,120 | (5.1,34.5) | [(1,2),(3,4)] | (3,4) | (-5,-12) | [(1,2),(3,4)]