<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: PostgreSQL: join_collapse_limit to force join order laid out by explicit JOINs	</title>
	<atom:link href="https://www.dbrnd.com/2019/02/postgresql-join_collapse_limit-to-force-join-order-laid-out-by-explicit-joins/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dbrnd.com/2019/02/postgresql-join_collapse_limit-to-force-join-order-laid-out-by-explicit-joins/</link>
	<description>BIGData &#124; NoSQL &#124; MSSQL &#124; MySQL &#124; PostgreSQL</description>
	<lastBuildDate>Mon, 21 Jan 2019 07:16:48 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.4</generator>
</channel>
</rss>
