Re: Lookup tables

e mys of clear. I don't see either and don' remember an occasion in over 20 years of DWH business the use of surrogates was a problem. > Either changing the color from GREE to YELLOW makes sense or it doesn't. Hear, hear. > If it doesn't make sense, then it's release which is faulty, not the > model. ACK Thiemo

Re: Lookup tables

El 05-02-25 a las 22:19, Michał Kłeczek escribió: But you can guarantee that if you change the value of the key after the user displays it - the user will get an error on submission (whereas with the surrogate key it would happily proceed without user noticing). As you very rightly say happil

Re: Lookup tables

El 05-02-25 a las 13:55, Michał Kłeczek escribió: A) Your release changed the sementics of the record 3. It's meaning changed. I cannot recommend doing that. That’s what using natural keys and FK’s restricting their changes guarantee: no (accidental) changes to meaning of data. Even with cas

Re: Lookup tables

El 05-02-25 a las 19:13, Michał Kłeczek escribió: Only if you do not see the primary key as the main immutable value identifying an object, entity, you name it. Surrogate key cannot identify any (real) object by definition :) What object is identified by PK value 42 in “restaurants” table? Wh

Re: Lookup tables

El 04-02-25 a las 18:08, Michał Kłeczek escribió: Reality tends to become so ambiguous as to not be reflectable (two entirely different restaurants eventually, within the flow of time, carry the very same name). A primary key is very likely not the proper place to reflect arbitrary business logi

Re: Lookup tables

04.02.2025 18:12:02 David G. Johnston : > On Tue, Feb 4, 2025 at 9:31 AM Michał Kłeczek wrote: > > Well, we were talking about lookup tables and not entity modelling... I am under the impression that a lookup table IS an entity. You find them in star and snowflake models alike. > >> >> Havi

Re: Lookup tables

04.02.2025 18:31:09 Michał Kłeczek : > >> On 4 Feb 2025, at 18:27, Thiemo Kellner wrote: >> >>  Unless the lookup table is actually a check constraint one can use to >> populate dropdown boxes in an interface. > > That is even worse because it ceases be

Re: Lookup tables

04.02.2025 18:31:09 Michał Kłeczek : >>  Unless the lookup table is actually a check constraint one can use to >> populate dropdown boxes in an interface. > > That is even worse because it ceases being transactional and users might > select something different than what they see on the screen.

Re: Lookup tables

Unless the lookup table is actually a check constraint one can use to populate dropdown boxes in an interface. Cheers Thiemo

Re: Display Bytea field

Maybe tools like DBeaver can help? It has a free trial period. Andy Hartman escribió: could it be done using Powershell? 

Re: Need help in database design

Just out of curiosity, not suggestion this is the solution. Why save json in PostgreSQL and not in a DB specialised on JSON like MongoDB? Divyansh Gupta JNsThMAudy escribió: Thank you everyone for giving your valuable responses, I am glad that everyone understands my concern. I got some go

Re: Plans for partitioning of inheriting tables

column constraints and table constraints. Not-null constraints are always copied to the new table./ 02.11.2024 00:53:53 Adrian Klaver : > On 11/1/24 16:10, thi...@gelassene-pferde.biz wrote: >> Adrian Klaver escribió: >> On 11/1/24 13:47, Thiemo Kellner wrote: >>>>

Re: Plans for partitioning of inheriting tables

Adrian Klaver escribió: On 11/1/24 13:47, Thiemo Kellner wrote: It looks to me basically to be a "create table A as select * from B where false". No it more capable then that. Yes, I wrote basically, not exactly. CREATE TABLE LIKE has like_option which allows to tra

Re: Plans for partitioning of inheriting tables

; "Unlike INHERITS, the new table and original table are completely decoupled > after creation is complete. Changes to the original table will not be applied > to the new table, and it is not possible to include data of the new table in > scans of the original table." > >&g

Re: Plans for partitioning of inheriting tables

Thanks, I shall have a look into it. I was under the assumption the the create table like would create no more than a structural copy. Torsten F��rtsch escribi��: Thiemo, �� it looks to me like you are using inheritance just to make sure your SOURCES and TOPO_FILES tables have

Re: Plans for partitioning of inheriting tables

Adrian Klaver escribió: Even if there where plans, any changes would happen in the future and would not be help the now problem. Yes and no. I can live without the partitioning, as I do not intend to load data from more than one source. Other might. But until others want to load data f

Re: Plans for partitioning of inheriting tables

Adrian Klaver escribió: Changing that would count as a major change. Even if you where to convince the developers to make the change the earliest it would released would be with the next major release in Fall of 2025. That assumes you can convince then early enough or at all. I was not

Re: Plans for partitioning of inheriting tables

TANCE-MAINTENANCE misses out on a sentence not to forget to adapt the triggers/rules. Kind regards Thiemo

Plans for partitioning of inheriting tables

Am 25.10.2024 um 17:57 schrieb Adrian Klaver: I do not feel it applies to my case. I tried to create a partitioned table that inherits columns from a base table. The documentation you provided the URL seems to speak of realising partitioning by using inheritance. This needs a code example

Re: Plans for partitioning of inheriting tables

Am 25.10.2024 um 17:57 schrieb Adrian Klaver: I do not feel it applies to my case. I tried to create a partitioned table that inherits columns from a base table. The documentation you provided the URL seems to speak of realising partitioning by using inheritance. This needs a code example

Re: Plans for partitioning of inheriting tables

Thanks for taking this up. 24.10.2024 22:44:11 Adrian Klaver : > > 1) Have you looked at?: > > https://www.postgresql.org/docs/current/ddl-partitioning.html#DDL-PARTITIONING-USING-INHERITANCE I do not feel it applies to my case. I tried to create a partitioned table that inherits columns from

Re: Plans for partitioning of inheriting tables

24.10.2024 22:58:39 David G. Johnston : > > My impression of things is that directly using “inherit” for table creation > is considered deprecated at this point.  No one has interest in expanding on > the feature nor even recommends it be used in new development.  That > particular unique featu

Plans for partitioning of inheriting tables

not find any hint in the documentation or in https://wiki.postgresql.org/wiki/Development_information. Kind regards Thiemo

Manual query vs trigger during data load

Hi To me it seems possible to create an insert select, e.g. Insert into tab1 (val1, val2) Select valA, valB >From tab2 Where valC = :param1 Cheers Thiemo

Re: Better way to process records in bash?

You maybe even could use plpythonu.

Better way to process records in bash?

Hi What is this "something" that it cannot be calculated within the dB?

Re: ssh to DB server and su normal users very slow :

Hi What does the server side do in the wait time? Cheers Thiemo

Re: Getting specific partition from the partition name

Thanks. Nice one. Would not have thought to try.

Re: [Code: 0, SQL State: 0A000] when "typing" from pg_catalog

Am 09.04.2024 um 17:18 schrieb Adrian Klaver: Because you did not do?: PG_CATALOG.PG_ROLES.ROLNAME%type Thanks

Re: [Code: 0, SQL State: 0A000] when "typing" from pg_catalog

Am 09.04.2024 um 17:18 schrieb Adrian Klaver: Because you did not do?: PG_CATALOG.PG_ROLES.ROLNAME%type Oh, right. Sorry. What an oversight.

Re: [Code: 0, SQL State: 0A000] when "typing" from pg_catalog

Thanks for taking this up. Am 09.04.2024 um 17:09 schrieb Adrian Klaver: On 4/9/24 07:59, Thiemo Kellner wrote: [Code: 0, SQL State: 0A000] ERROR: References to other databases are not implemented: pg_catalog.pg_roles.rolname    Position: 298 [Script position: 334 - 361

[Code: 0, SQL State: 0A000] when "typing" from pg_catalog

schema not a database, like information_schema. Am I missing something? And why is it not allowed to type from the catalogue? I presume, this example is rather academic due to the name type. Kind regards Thiemo create or replace function GRANT_SELECTS() returns void language plpgsql as $body

Re: Is this a buggy behavior?

Am 25.03.2024 um 07:59 schrieb Laurenz Albe: On Sun, 2024-03-24 at 17:32 +0100, Thiemo Kellner wrote: How can that be forgotten? This information ends up in the data catalogue eventually! It *is* stored in the catalog. But if you add a primary key, that is tantamount to saying ALTER

Re: Empty materialized view

My bad as always. Having the refresh after the filling of the tables does the trick. Thanks for your help.

Re: Empty materialized view

Am 24.03.2024 um 22:06 schrieb Adrian Klaver: The view session is on auto commit. (It's sole purpose to query stuff and not to have explicitly terminate transactions do to syntax errors and so on.) Autocommit will only affect actions in that session, it will not make the other sessions action

Re: Empty materialized view

Am 24.03.2024 um 21:50 schrieb Adrian Klaver: On 3/24/24 13:36, Thiemo Kellner wrote: It does depending on the order of viewing. Namely if you viewed the 'old' empty MV in the outside session before you dropped/created the 'new' MV and committed the changes. Someth

Re: Empty materialized view

Am 24.03.2024 um 21:30 schrieb Adrian Klaver: On 3/24/24 13:11, Thiemo Kellner wrote: Confirmed in the same session that created it or in a different session? Different session, not knowing what that mattered. Excerpt of the installation protocol: … ## tenth level ## Set materialised view

Re: Empty materialized view

Am 24.03.2024 um 20:56 schrieb Erik Wienhold: Maybe you executed REFRESH in a transaction but did not commit it? While I can see the point for the refresh (but there actually is a commit), I cannot hold it valid for a create with data when the mv actually is created (confirmed by being empt

Empty materialized view

ode attached. Kind regards Thiemo snowrunner.7z Description: application/compressed

Re: Is this a buggy behavior?

Am 24.03.2024 um 17:43 schrieb Christophe Pettus: The situation is much more like the customer saying, "I understand that the standard paint for this car is red, but I wish it painted blue instead." Not in the least. Declaring the column to be NULL is explicitly requesting the car be blue. An

Re: Is this a buggy behavior?

Am 24.03.2024 um 17:15 schrieb Christophe Pettus: I think the point is that it's not really doing anything "silently." You are asking for a PRIMARY KEY constraint on a column, and it's giving it to you. One of the effects (not even really a side-effect) of that request is that the column i

Re: Is this a buggy behavior?

Am 24.03.2024 um 16:44 schrieb Andreas Kretschmer: postgres=# create table bla(i int null primary key); CREATE TABLE postgres=# \d bla     Table "public.bla"  Column |  Type   | Collation | Nullable | Default +-+---+--+-  i  | integer

Re: Is this a buggy behavior?

Am 24.03.2024 um 16:35 schrieb sud: On Sun, Mar 24, 2024 at 8:47 PM Tom Lane > wrote: Do you specifically mean that 'null'  keyword is just not making any sense here in postgres. But even if that is the case , i tried inserting nothing (hoping "nothing" is "null" in

Re: Is this a buggy behavior?

Am 24.03.2024 um 16:39 schrieb Erik Wienhold: And that's also possible in Postgres with UNIQUE constraints if you're looking for that behavior. Sort of the distinction between PK and UQ.

Re: Is this a buggy behavior?

Am 24.03.2024 um 16:36 schrieb Andreas Kretschmer: the null-able constraint addition to a column is pointless because by default all columns are nullable. definition as a primary key adds the not null constraint. While this is certainly true, I do not see why the information that a not nul

Re: Is this a buggy behavior?

Am 24.03.2024 um 16:17 schrieb Tom Lane: To do that, we'd have to remember that you'd said NULL, which we don't: the word is just discarded as a noise clause. Considering that this usage of NULL isn't even permitted by the SQL standard, that seems like a bit too much work. If I understood c

Re: Is this a buggy behavior?

correct, is not too concise. I wished, that PG issued a warning about a definition conflict. In PostgreSQL, a PK must always be not nullable, so explicitly defining on of a PK's columns as nullable is contradictory, one should get notified of. The two dimes of Thiemo

Re: PostgreSQL as advanced job queuing system

Am 22.03.2024 um 14:15 schrieb Fred Habash: We developed a home-grown queue system using Postgres, but its performance was largely hindered by que tables bloating and the need to continuously vacuum them. It did not scale whatsoever. With some workarounds, we ended up designing three sets of

Re: select results on pg_class incomplete

https://wiki.postgresql.org/wiki/Monitoring Thanks for the URL. I am not too keen to re-invent the wheel. Although it teaches me on PostgreSQL.

Re: select results on pg_class incomplete

You could also create a PostgreSQL foreign server for each of the other databases, which would let you issue a query to UNION together the results of a query on all of the catalogs. This would require creating a foreign table for pg_class in the other databases. Thanks. So many possibilit

Re: select results on pg_class incomplete

You solve a problem that no one has. Data belonging together may still be divided into schemas in a database. Thus, the metadata is also reported and archived individually per database. I am not sure, we are taking about the same problem, but would be surprised to be the only one having exper

Re: select results on pg_class incomplete

Am 14.03.2024 um 21:03 schrieb David Rowley: Yeah, maybe dblink and a LATERAL join might be an easy way. Something like: create extension dblink; select d.datname,c.relname from pg_database d, lateral (select * from dblink('dbname='||d.datname,$$select relname from pg_class where relname = 'p

Re: select results on pg_class incomplete

Thanks for the enlightenment. A pity. I suppose, there is no working around this? Am 14.03.2024 um 18:01 schrieb Adrian Klaver: On 3/14/24 09:41, Thiemo Kellner wrote: Hi I am trying to access PostgreSQL meta data, possibly in a vane attempt to get size data. I use DbVis with a connection

select results on pg_class incomplete

es, listed what is in the database one connects to - https://ibb.co/dbbJVbJ. template1=> select count(*) from PG_CLASS where RELNAME = 'umsaetze'; count --- 0 (1 row) template1=> \q C:\Users\thiemo\AppData\Roaming\MOBAXT~1\home>psql -h hp-slimline-260 -p 5436 -U

Re: Me again with an insert trigger problem

Am 27.02.2024 um 23:20 schrieb Adrian Klaver: On 2/27/24 14:11, Thiemo Kellner wrote: It is a habit of mine to pad conditions in the where clause. This way, it is easy to comment/uncomment parts of the clause for testing purposes. Coming from Oracle, I missed that using "true&quo

Re: Me again with an insert trigger problem

Am 27.02.2024 um 21:42 schrieb Adrian Klaver: Also not sure what this: select NODE_TYPE⠒NAME into V⠒NODE_TYPE⠒NAME   from NODE⠒V where 1 = 1    and ID = new.NODE⠒ID    and 1 = 1; is supposed to be doing especially the 1 = 1 tests? The selec

Re: Me again with an insert trigger problem

Thanks. 27.02.2024 19:09:50 Adrian Klaver : > > On 2/27/24 9:49 AM, Thiemo Kellner wrote: >> Hi >> >> I am surprised that my before insert trigger function does not insert any >> rows into NODE_GOOD. >> >> I was under the impression that the trigger

Me again with an insert trigger problem

output of the important part of the install script is listed at the end. Please find attached my code. Kind regards Thiemo insert data into NODE_GOOD⠒V psql:insert_data/NODE_GOOD⠒V.pg_sql:27: INFO: new.NODE⠒ID: 1107cb8d-c1f1-4368-ac7b-72ac3031555a psql:insert_data/NODE_GOOD⠒V.pg_sql:27: INFO: n

Re: pPL/pgSQL restriction on characters for copying types?

Shame on me. My bad. It was the order of installation that did not work. Sorry for that. I was mislead by the error message. If an object is missing I would not expect an invalid type name message. Thanks Am 26.02.2024 um 17:53 schrieb Thiemo Kellner: Thanks for the hint and care. The install

Re: pPL/pgSQL restriction on characters for copying types?

Thanks for the hint and care. The install script has a set statement already and I now added the search_path clause to no avail. Please find the entire code attached and a screenshot from the error. Am 26.02.2024 um 17:35 schrieb Tom Lane: Thiemo Kellner writes: However, I want to create a

Re: pPL/pgSQL restriction on characters for copying types?

Oh, I totally forgot to mention that I ran the scripts with DbVisualizer against a 16.1 (Debian 16.1-1.pgdg110+1) server using PostgreSQL JDBC Driver 42.6.0 . Am 26.02.2024 um 16:51 schrieb Thiemo Kellner: Hi My names can contain a special character (⠒), e.g. to separate the donator object

pPL/pgSQL restriction on characters for copying types?

_TYPE⠒NAME text; Please find attached script files of objects directly involved in the trigger function. Is there something, I am doing wrongly? Kind Regards Thiemo@echo Set up function NODE_GOOD⠒TR_B_IU_R; set search_path = snowrunner, public; create or replace function NODE_GOOD⠒TR_B_IU_R()

Re: client/server versions

Am 21.11.2023 um 13:18 schrieb Dick Visser: It is possible, it's just that there is no real need to at the moment, ao we have not spent that much effort on the topic. At any time there will always be newer upstream versions. Ok, fair enough, but it puzzles me that the effort shall be put int

Re: client/server versions

Hi Dick Out of curiosity, what is the reason there is this zoo of versions. Is it impossible to align them to one version? Cheers Thiemo

Re: Conditional compilation

checks for every and each logging statement put (as the check has been done on installation already). begin     do_something;     $if check_if_env_is_dev $then         do_some_logging;     $end     do_more_stuff; end; Am 12.11.2023 um 16:58 schrieb Tom Lane: Ron writes: On 11/12/23 09:

Conditional compilation

ts of single statements. I suppose it is sort of a preprocessor that removes the code part from $IF until $END if the condition is not met. Kind regards Thiemo

Re: Detection of which attributes should get set in update trigger

Thanks for the reply. I confirm the behaviour. Your explanation makes sense if I consider having read that with an update the is a complete new record version written. Am 10.11.2023 um 14:35 schrieb David G. Johnston: On Friday, November 10, 2023, Thiemo Kellner wrote: Hi all I

Detection of which attributes should get set in update trigger

se new.XYZ end; And what about the where condition... hm, guess I am a bit confused. Kind regards Thiemo

Rule system (and triggers)

ode = 'AG'; c) I noticed that, even though the rules define logic for the other attributes, those do not get changed if not present in an update. While this is actually good, but surprises me nonetheless. Did I miss some reading in the doc? Must I use trig

Re: need SQL logic to find out way's to Implement check sum to validate table data is migrated correctly

advantage that you could, if you wanted, also implement logic to tell you precisely in which columns the difference is encountered. Kind regards Thiemo Am 27.10.2023 um 10:56 schrieb Y_esteembsv-forum: Hi Need SQL logic/different approach method's  to find out way's a) to Implement ch

Purely declarative FKs

hardly ever a modelling tool involved. Kind regards Thiemo

Re: an difficult SQL

sets end it is not always easy to get ones head around thinking in sets. I hope you could follow my suggestions. It might not be the most efficient way but should work. Kind regards Thiemo Am 05.11.22 um 16:10 schrieb Rafal Pietrak: Hi Everybody, I was wondering if anybody here could help

Re: Window function?

. Kind regards Thiemo Am 04.06.22 um 10:18 schrieb Robert Stanford: Hi, I have time series data from multiple inputs with start and end timestamps. Can anyone suggest an elegant way to coalesce consecutive rows so only the first start time and last end time for each group of events (by input) is

Re: How to check if a materialised view is being updated?

I’ve got a materialized view as a source for my ETL-process, and the materialized view takes several hours to refresh. During which it is locked for queries. Would it be an option to split the process into a cascade of materialized views to minimize the actual time of lock? So I’m lookin

Re: Do we need a way to moderate mailing lists?

comparison to using something like pastebin.com? I only found very coarse instructions on what to do on the lists. Have I been missing a link to a netiquette page? Cheers Thiemo -- S/MIME Public Key: https://oc.gelassene-pferde.biz/index.php/s/eJuAUFONag6ofnH Signal (Safer than WhatsApp): +49

Re: Suggestion: provide a "TRUNCATE PARTITION" command

Quoting Michael Lewis : Still, no feedback on the effect that a truncate call is having on the DB and may be doing more than intended fairly easily. I am not in the hackers group so I couldn't say this feature would not be implemented. It just seems unlikely given the philosophies of that

Re: Possible trigger bug? function call argument literalised

Quoting Adrian Klaver : On 1/3/21 1:44 PM, Thiemo Kellner wrote: So is the below still only going to fire on INSERT? If so it will not deal with functions that disappear after the INSERT, which in the end makes it similar to my suggestion:) The point being you are taking a snapshot in

Re: Possible trigger bug? function call argument literalised

Quoting Adrian Klaver : Familiar with it, I have worked in farming(outdoor and indoor(greenhouse)) industries. Cool (https://en.wikipedia.org/wiki/Growing_degree-day). It is a measure for energy an organism can consume in a specific day for its development. Also used to anticipate pe

Re: Possible trigger bug? function call argument literalised

Quoting Adrian Klaver : Can you provide an outline form of what you are trying to accomplish? Hm, making myself understood. ;-) So from the very beginning. There is the concept of growing degree days (https://en.wikipedia.org/wiki/Growing_degree-day). It is a measure for energy an organis

Re: Possible trigger bug? function call argument literalised

Quoting Adrian Klaver : Well, I guess, I can put the correct schema at installation, but would have liked to have a more general approach. Furthermore, I think this also implies that installation can only be done by psql. :-s Why not grab the CURRENT_SCHEMA in the function?: DECLARE

Re: Possible trigger bug? function call argument literalised

Quoting Tom Lane : Thiemo Kellner writes: create trigger CALCULATION_METHOD_BR_IU before insert on CALCULATION_METHOD for each row execute function METHOD_CHECK(current_schema); Executing such, the string "current_schema" gets literalised, i.e. single quoted: Yu

Re: Possible trigger bug? function call argument literalised

Quoting Rob Sargent : The function definition doesn’t name any parameters? Nope, trigger functions cannot, according to documentation. Parameters can be passed as list/array of values though. I have no clue about why this needs to be so awful/awesome. -- S/MIME Public Key: https:

Re: Possible trigger bug? function call argument literalised

end if; insert into TG_TABLE_SCHEMA.TG_TABLE_NAME values (NEW.*); return NULL; end; $body$; Running this version, I get another proof that the term was literalised: psql:common_calculation_method_insert.pg_sql:59: ERROR: Schema "current_schema" could not be foun

Possible trigger bug? function call argument literalised

gly feel this is a bug, at least no intention at all from my side. However, before filing a bug, I wanted to get your opinion on that. Maybe it is just a problem of the openSUSE Tumbleweed repository. I would appreciate your two dimes. Kind regards Thiemo -- S/MIME Public Key: https://oc.gelasse

Re: SQL pretty pritner?

https://www.sqlinform.com/ Quoting stan : I have a presentation later in the week, and i plan on printing out some files containing SQL commands. I have used some "pretty printers" in the past for things like Perl scripts. What I am thinking of s something that bolds keywords, handles page brea

pgutils, pglogger and pgutilsL out

pgutilsL are small but it is a beginning after all. :-) Kind regards Thiemo -- S/MIME Public Key: https://oc.gelassene-pferde.biz/index.php/s/eJuAUFONag6ofnH Signal (Safer than WhatsApp): +49 1578 7723737 Handys: +41 78 947 36 21 | +49 1578 772 37 37 Tox-Id

Re: Use of ?get diagnostics'?

k does not include the error place in dynamic SQL executed by the "execute" command. Maybe I am missing something again. Kind regards Thiemo -- S/MIME Public Key: https://oc.gelassene-pferde.biz/index.php/s/eJuAUFONag6ofnH Signal (Safer than WhatsApp): +49 1578 7723737 Handys: +41 78

Re: Use of ?get diagnostics'?

Hi Andrew Paste sites are for IRC, on the mailing list you should always attach the necessary details to your message. Ok, I was under the impression that paste site were preferable to attachments which generates traffic not everyone is interested in. Thiemo> the following except

Use of ?get diagnostics'?

set PROPERTY_VALUE_STRING = I_LEVEL where PROPERTY_NAME = C_LOGGING_LEVEL_PROPERTY_NAME; get current diagnostics V_ROW_COUNT = ROW_COUNT; I did not find the error I am making. Kind regards Thiemo -- S/MIME Public Key: https://oc.gelassene-pferde.biz/index.php/s/eJuAUFONag6ofnH Signal (Safer than W

Re: Posible off topic ? pgmodeler

I suppose at least major Linux distributions provide a package of a more or less recent version of it. Ubuntu does anyway. I am not aware of an other binary distributor but Raphael for Windows or Mac, but then again those are not my turf. Kind regards Thiemo -- S/MIME Public

Re: pgmodeler ?

update in preparation in 0.92 which should. You may want to givi it a try.   Actually, this is a known problem: https://github.com/pgmodeler/pgmodeler/issues/1281 Maybe you want to give the beta a shot: https://pgmodeler.io/download Kind regards Thiemo S/MIME Public Key: https://oc

Re: timestamp out of range while casting return value to function's return type

Hi Karsten Thanks for the infinitly good hint. I remembered the infinity blurredly somewhen this morning, looked it up in the docs and already dumped my functions in favour of the infinity solution. :-) Great, that PostgreSQL has the infinity concept! Thanks Kind regards Thiemo Quoting

Re: timestamp out of range while casting return value to function's return type

Hi Tom Thanks for replying so fast. You are absolutely right. I changed the code file but failed to install it. :-( I am sorry for not checking the obvious. Kind regards Thiemo Quoting Tom Lane : Thiemo Kellner writes: I created a function that ought to return a timestamptz (another

timestamp out of range while casting return value to function's return type

-- highest timestamps on 64bit lubuntu vanilla PostgreSQL 11.3 return '294277-01-01 00:59:59.99'::timestamptz; end; $body$; Kind regards Thiemo -- S/MIME Public Key: https://oc.gelassene-pferde.biz/index.php/s/eJuAUFONag6ofnH Signal (Safer than WhatsApp): +49 1578 7723737 Hand

Re: Need a DB layout gui

You also could try out DBVisualizer (https://www.dbvis.com/). It is available in a feature reduced free version. Feautre comaprison is at https://www.dbvis.com/features/feature-list/. I personally bought the pro to support development. I rarely use a pro feature. Quoting Zahir Lalani : Nav

Re: sequences

Hi Karl I did not double check with the doc whether the SQL you posted is valid (I guess it could by applying the defaults) however I do not see how sequences would govern the sending of data to users. Kind regards Thiemo Quoting Karl Martin Skoldebrand : Hi, I'm tryi

Re: Table inheritance over schema boundaries possible

Quoting Achilleas Mantzios : as of 10 (same with 11) you (IL) must be the owner of relation SCD.TEMPL_BK . Create your tables with a user who has correct privileges on both tables/schemas. Not what I hope for but was afraid of. thank you for the answer. -- Achilleas Mantzios IT DEV Lead I

Table inheritance over schema boundaries possible

denied for schema scd Even though I granted all privileges to IL. What am I missing or is it just not possible what I want to do? Kind regards Thiemo -- S/MIME Public Key: https://oc.gelassene-pferde.biz/index.php/s/eJuAUFONag6ofnH Signal (Safer than WhatsApp): +49 1578 7723737 Handys: +41 78 947

Re: POSTGRES/MYSQL

to overhaul your application. Kind two dimes Thiemo -- Signal: +49 1578 7723737 Handys: +41 78 947 36 21 | +49 1578 772 37 37 Tox-Id: B7282A9E31D944DDAD1ECC5B33C36AAE80B32D119AB7391D602C937A65E8CA0625C495C5322B

Re: Is there something wrong with my test case?

Hi Fabio Quoting Fabio Pardi : The cost is not a range. The 2 numbers you see are: * Estimated start-up cost. This is the time expended before the output phase can begin, e.g., time to do the sorting in a sort node. *Estimated total cost. This is stated on the assumption that

  1   2   >