Zur Kurzanzeige

dc.contributor.authorHirn, Denis
dc.contributor.editorMeyer, Holger
dc.contributor.editorRitter, Norbert
dc.contributor.editorThor, Andreas
dc.contributor.editorNicklas, Daniela
dc.contributor.editorHeuer, Andreas
dc.contributor.editorKlettke, Meike
dc.date.accessioned2019-04-15T11:40:35Z
dc.date.available2019-04-15T11:40:35Z
dc.date.issued2019
dc.identifier.isbn978-3-88579-684-8
dc.identifier.issn1617-5468
dc.identifier.urihttp://dl.gi.de/handle/20.500.12116/21811
dc.description.abstractPlan forcing is the most capable plan hinting that a database system can implement. It allows the specification of almost every aspect of an execution plan. The open source database system PostgreSQL does not implement any plan hints by default. We will show how an extension can be used to provide plan forcing for PostgreSQL. This extension allows to use the query executor directly and independently of SQL. We sketch some of the interesting use case scenarios for plan forcing in PostgreSQL.en
dc.language.isoen
dc.publisherGesellschaft für Informatik, Bonn
dc.relation.ispartofBTW 2019 – Workshopband
dc.relation.ispartofseriesLecture Notes in Informatics (LNI) – Proceedings, Volume P-290
dc.subjectPostgreSQL
dc.subjectPhysical Algebra
dc.subjectPlan Tree Execution
dc.subjectQuery Unnesting
dc.titlePgCuckoo – Injecting Physical Plans into PostgreSQLen
mci.reference.pages235-244
mci.conference.sessiontitleStudierendenprogramm
mci.conference.locationRostock
mci.conference.date4.-8. März 2019
dc.identifier.doi10.18420/btw2019-ws-24


Dateien zu dieser Ressource

Thumbnail

Zur Kurzanzeige