> which queries produced which rows

I doubt many real-world applications could tolerate the amount of data/performance degradation this implies. If you need this (and I can't think why you would), then I think writing your own logging code is the answer, rather than lumbering everyone else with it.

▲ rbanffy 14 minutes ago | parent [-]

If they did it efficiently, then they might have a game changer.

	▲	zabzonk a minute ago \| parent [-]
		Well, you can do it efficiently as you like, but if the data is to be historically accurate on a writeable table then if we are recording `SELECT * FROM foobar` it is likely to require a copy of foobar at the time of the query, or doing amazing things with the transaction log. I agree this would be a programming tour de force, but I question its utility.