hubert depesz lubaczewski writes:
> I have weird situation.
> pg 9.1.2, compilet by our own script from source, on 10+ machines.
> on fours machines, pg_dump -s - dumps with data!:
> postgres@machine:~$ pg_dump --verbose --schema-only dbname > q
> ...
> pg_dump: creating TABLE x1
> pg_dump: res
On 01/27/2012 03:05 PM, hubert depesz lubaczewski wrote:
On Fri, Jan 27, 2012 at 03:00:24PM -0800, Adrian Klaver wrote:
On 01/27/2012 02:19 PM, hubert depesz lubaczewski wrote:
hiu
I have weird situation.
pg 9.1.2, compilet by our own script from source, on 10+ machines.
on fours machines, pg_d
On Fri, Jan 27, 2012 at 03:00:24PM -0800, Adrian Klaver wrote:
> On 01/27/2012 02:19 PM, hubert depesz lubaczewski wrote:
> >hiu
> >I have weird situation.
> >pg 9.1.2, compilet by our own script from source, on 10+ machines.
> >on fours machines, pg_dump -s - dumps with data!:
>
> Are those 4 ma
On 01/27/2012 02:19 PM, hubert depesz lubaczewski wrote:
hiu
I have weird situation.
pg 9.1.2, compilet by our own script from source, on 10+ machines.
on fours machines, pg_dump -s - dumps with data!:
Are those 4 machines different from the other 6+?
What does the script do?
I am guessing you
hiu
I have weird situation.
pg 9.1.2, compilet by our own script from source, on 10+ machines.
on fours machines, pg_dump -s - dumps with data!:
postgres@machine:~$ pg_dump --verbose --schema-only dbname > q
...
pg_dump: creating TABLE x1
pg_dump: restoring data for table "x2"
pg_dump: dumping c
Il giorno ven, 27/01/2012 alle 12.38 -0500, Tom Lane ha scritto:
> > NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
> > "bcbydocinfo_pk" for table "barcodebydocumentinfo"
> > ERROR: permission denied for relation documents
>
> This example works for me. Are you sure you are exec
Hello,
I have a problem about dropping and recovering foreign key constraint.
Since we are using table partitioning for table A, records are always directed
to one partition by triggers, leaving the parent table A empty.
However, for table B where A's id serves as a foreign key, the foreign key
Giuseppe Sacco writes:
> I get this error while executing a CREATE TABLE statement.
> This is my CREATE statement:
> CREATE TABLE agenzia.BarcodeByDocumentInfo (
> docId VARCHAR(17) NOT NULL,
> defaultOp VARCHAR(10) NOT NULL DEFAULT 'Append',
> CONSTRAINT BcByDocInfo_pk PR
Il giorno ven, 27/01/2012 alle 08.54 -0800, Adrian Klaver ha scritto:
> On Friday, January 27, 2012 8:25:56 am Giuseppe Sacco wrote:
[...]
> > I am owner of table "documents":
> >
> > neos=> \dt agenzia.documents
> > List of relations
> > Schema | Name| Type | Owner
> >
On Friday, January 27, 2012 8:25:56 am Giuseppe Sacco wrote:
> Hi,
> I get this error while executing a CREATE TABLE statement.
> This is my CREATE statement:
>
> CREATE TABLE agenzia.BarcodeByDocumentInfo (
> docId VARCHAR(17) NOT NULL,
> defaultOp VARCHAR(10) NOT NULL DEFAULT 'Ap
Hi,
I get this error while executing a CREATE TABLE statement.
This is my CREATE statement:
CREATE TABLE agenzia.BarcodeByDocumentInfo (
docId VARCHAR(17) NOT NULL,
defaultOp VARCHAR(10) NOT NULL DEFAULT 'Append',
CONSTRAINT BcByDocInfo_pk PRIMARY KEY (docId),
CONST
On Friday, January 27, 2012 7:44:55 am bbo...@free.fr wrote:
> Hello!
>
> again quite a stupid problem i regularly run into
> and that i still haven't solved yet...
>
> again i used a type timestamp to keep a track of modification time, and
> again it gets stupid and confusing.
>
> first
On 1/27/2012 9:44 AM, bbo...@free.fr wrote:
Hello!
again quite a stupid problem i regularly run into
and that i still haven't solved yet...
again i used a type timestamp to keep a track of modification time, and again
it gets stupid and confusing.
first of all the errors are labeled a
Daniel,
just use different fts configuration for search, which doesn't
includes stemmers.
Regards,
Oleg
On Fri, 27 Jan 2012, Daniel V?zquez wrote:
Hi guys!
Full text search, searches by lexemes, this minds that if you are finding
for "gato" word you are really finding for {gat} lexeme.
I you
On Friday, January 27, 2012 7:44:55 am bbo...@free.fr wrote:
> Hello!
>
> again quite a stupid problem i regularly run into
> and that i still haven't solved yet...
>
> again i used a type timestamp to keep a track of modification time, and
> again it gets stupid and confusing.
>
> first
Hello!
again quite a stupid problem i regularly run into
and that i still haven't solved yet...
again i used a type timestamp to keep a track of modification time, and again
it gets stupid and confusing.
first of all the errors are labeled as timestamp without timezone, i only
specifie
Hi guys!
Full text search, searches by lexemes, this minds that if you are finding
for "gato" word you are really finding for {gat} lexeme.
I you construct vectors for the words "gato", "gatos", "gata", "gatas", all
have the same lexema {gat}
Then the search "gato" that is to say the search {gat}
Hi guys!
Full text search, searches by lexemes, this minds that if you are finding
for "gato" word you are really finding for {gat} lexeme.
I you construct vectors for the words "gato", "gatos", "gata", "gatas", all
have the same lexema {gat}
Then the search "gato" that is to say the search {gat}
Didn't reply-all
Begin forwarded message:
> From: David Johnston
> Date: January 27, 2012 9:01:37 EST
> To: John Tuliao
> Subject: Re: [SQL] Query question
>
> On Jan 26, 2012, at 7:00, John Tuliao wrote:
>
>> I seem to have a problem with a specific query:
>>
>> The inside query seems
Hi
> "DK" == Dmitry Koterov writes:
DK> create table a(i integer);
DK> CREATE UNIQUE INDEX a_idx ON a USING btree (i);
DK> CREATE FUNCTION a_tr() RETURNS trigger AS
DK> $body$
DK> BEGIN
DK> DELETE FROM a WHERE i = NEW.i;
DK> RETURN NEW;
DK> END;
DK> $body$
DK> LANGUAGE 'plpgsql';
DK>
On Fri, Jan 27, 2012 at 1:28 AM, Eduardo Morras wrote:
> At 00:32 27/01/2012, you wrote:
>
> There are cases where intraquery parallelism would be helpful. As far as
>> I understand it, PostgreSQL is the only major, solid (i.e. excluding MySQL)
>> RDBMS which does not offer some sort of intraqu
At 00:32 27/01/2012, you wrote:
There are cases where intraquery parallelism would be helpful. As
far as I understand it, PostgreSQL is the only major, solid (i.e.
excluding MySQL) RDBMS which does not offer some sort of intraquery
parallelism, and when running queries across very large datab
On Fri, Jan 27, 2012 at 00:32, Chris Travers wrote:
>
>
> On Thu, Jan 26, 2012 at 3:02 PM, Merlin Moncure wrote:
>>
>> On Thu, Jan 26, 2012 at 3:52 PM, Rodrigo E. De León Plicet
>> wrote:
>> > Quote:
>> >
>> > ==
>> >
>> > This
Quoth "David Johnston" :
> A) SELECT user_id, CASE WHEN course_name = 'Maths' THEN completed ELSE false
> END math_cmp, CASE WHEN course_name = 'English' THEN completed ELSE false
> END AS english_cmp FROM applications
> a) Expand to multiple columns and store either the default "false" or the
24 matches
Mail list logo
