On 9/9/15 7:44 PM, David G. Johnston wrote:
On Wed, Sep 9, 2015 at 7:53 PM, Charles Sheridan <mailto:cesh...@swbell.net>>wrote:
Hi All,
When there are several views defined on top of each other, are
SELECTs on views that do not specify a SORT order guaranteed to
pre
Hi All,
When there are several views defined on top of each other, are SELECTs
on views that do not specify a SORT order guaranteed to preserve the
cumulative sort order of the lower-level views ?
Is the answer true for any arbitrarily large set of layered views?
Is the answer the same if th
Hi,
I was looking at PL/pgSQL documentation and realized that contrary to
spec, I've been omitting the colon ':' from assignments, e.g. writing
'x = 5' rather than the correct
'x := 5'
I don't see any error messages about this.
I am not aware of any problems due to this. I suppose that i
n for these cols to identify that they have auto-generated
indices.
Best, Charles
On 13-08-19 8:42 AM, Andrew Dunstan wrote:
On 08/19/2013 09:10 AM, Charles Sheridan wrote:
Hi,
I don't see indication that the capability described below exists in
Postgres (or any RDBMS), so this is likely
In my use, mainly arrays and hstore cols, including arrays of hstores.
These are column types that I suspect benefit from indexes more than
most column types.
Charles
On 13-08-19 8:14 AM, Pavel Stehule wrote:
Hello
2013/8/19 Charles Sheridan <mailto:cesh...@swbell.net>>
H
n addition to a table. In the case of CREATE TABLE,
this would be less of a concern, and more of a concern for ALTER TABLE
ADD COLUMN.
Such a configuration would also specify the type of index.
What do you think ?
Thanks,
Charles Sheridan
--
Sent via pgsql-hackers mailing list (pgs
