On 01/17/2015 10:05 AM, Berend Tober wrote:
I often work with the output of pg_restore from a custom format dump
file. For example a file produced by running
pg_restore -s -1 -L listfile dumpfile
where listfile has been edited to comment out most of the rows to leave
only the data base objects
Berend Tober wrote on 17.01.2015 19:05:
I often work with the output of pg_restore from a custom format dump
file. For example a file produced by running
pg_restore -s -1 -L listfile dumpfile
where listfile has been edited to comment out most of the rows to
leave only the data base objects I'm
I often work with the output of pg_restore from a custom format dump
file. For example a file produced by running
pg_restore -s -1 -L listfile dumpfile
where listfile has been edited to comment out most of the rows to leave
only the data base objects I'm currently interested in.
Most often,
Adrian Klaver wrote:
On 01/17/2015 10:05 AM, Berend Tober wrote:
I often work with the output of pg_restore from a custom format dump
file. ...
Most often, I'm refactoring functions and so don't really want to drop
the function but rather want to do a create or replace function...
Not sure
On 01/17/2015 10:05 AM, Berend Tober wrote:
I often work with the output of pg_restore from a custom format dump
file. For example a file produced by running
pg_restore -s -1 -L listfile dumpfile
where listfile has been edited to comment out most of the rows to leave
only the data base objects
Adrian Klaver wrote:
On 01/17/2015 10:05 AM, Berend Tober wrote:
I often work with the output of pg_restore from a custom format dump
file...
Most often, I'm refactoring functions and so don't really want to drop
the function but rather want to do a create or replace function...
I am not
Thomas Kellerer wrote:
Berend Tober wrote on 17.01.2015 19:05:
I often work with the output of pg_restore from a custom format dump
file. ...
Most often, I'm refactoring functions and so don't really want to
drop the function but rather want to do a create or replace
function ...
To me this
On Sat, Jan 17, 2015 at 11:18 PM, Kouhei Sutou k...@cozmixng.org wrote:
(Is this mailing list right mailing list for asking this
question...?)
Hackers would have been fine as well.
Is there any plan to implement PostgreSQL API to implement
WAL supported extension?
Not that I know of, the last
All,
I have a Rails application on 9.3 in which I want to enforce a unique
index on a set of fields, one of which includes a NULL-able column.
According to
http://www.postgresql.org/docs/9.3/static/indexes-unique.html, btree
indexes can't handle uniqueness on NULL columns, so I'm looking
On Sat, Jan 17, 2015 at 6:27 AM, Peter Hicks peter.hi...@poggs.co.uk
wrote:
All,
I have a Rails application on 9.3 in which I want to enforce a unique
index on a set of fields, one of which includes a NULL-able column.
According to
Hi John
On 17/01/15 12:39, John McKown wrote:
I read the above. As I understand it, you can have a unique index on
a column which is NULL-able. That will guarantee that all the non-NULL
values are unique. What it will not guarantee is that there will be at
most one NULL value in the indexed
Peter Hicks peter.hi...@poggs.co.uk wrote:
All,
I have a Rails application on 9.3 in which I want to enforce a unique
index on a set of fields, one of which includes a NULL-able column.
According to
http://www.postgresql.org/docs/9.3/static/indexes-unique.html, btree
indexes can't
Hi,
(Is this mailing list right mailing list for asking this
question...?)
Is there any plan to implement PostgreSQL API to implement
WAL supported extension?
Background:
I'm writing an extension(*) that provides index module for CJK
ready fast full-text search feature.
(*) PGroonga:
13 matches
Mail list logo