On Sun, Feb 28, 2010 at 10:23 PM, Terry wrote:
> On Sun, Feb 28, 2010 at 7:12 PM, John R Pierce wrote:
>> Terry wrote:
>>>
>>> One more question. This is a pretty decent sized table. It is
>>> estimated to be 19,038,200 rows. That said, should I see results
>>> immediately pouring into the des
On Sun, Feb 28, 2010 at 7:12 PM, John R Pierce wrote:
> Terry wrote:
>>
>> One more question. This is a pretty decent sized table. It is
>> estimated to be 19,038,200 rows. That said, should I see results
>> immediately pouring into the destination table while this is running?
>>
>
> SQL transa
"C. Bensend" writes:
>I'm playing around with putting some of my email system's config
> into PostgreSQL, and I ran into some behavior I didn't expect today.
> ...
>I added the postfix user to pg_hba.conf and reloaded PostgreSQL:
Generally speaking you don't want to make per-user entrie
Hey folks,
I'm playing around with putting some of my email system's config
into PostgreSQL, and I ran into some behavior I didn't expect today.
I'm sure this is just misunderstanding on my part, but reading the
documentation hasn't cleared it up for me yet.
This is PostgreSQL 8.4.2 on Ope
Terry wrote:
One more question. This is a pretty decent sized table. It is
estimated to be 19,038,200 rows. That said, should I see results
immediately pouring into the destination table while this is running?
SQL transactions are atomic. you wont' see anything in the 'new' table
until
On Sun, Feb 28, 2010 at 6:29 PM, John R Pierce wrote:
> Szymon Guz wrote:
>>
>> Different doesn't mean that the id should be greater or lower, rather
>> should be different. I'd rather do something like:
>
> indeed, my code assumed that records were only INSERT'd into table1 and
> never UPDATE or
On Sun, Feb 28, 2010 at 6:29 PM, John R Pierce wrote:
> Szymon Guz wrote:
>>
>> Different doesn't mean that the id should be greater or lower, rather
>> should be different. I'd rather do something like:
>
> indeed, my code assumed that records were only INSERT'd into table1 and
> never UPDATE or
Szymon Guz wrote:
Different doesn't mean that the id should be greater or lower, rather
should be different. I'd rather do something like:
indeed, my code assumed that records were only INSERT'd into table1 and
never UPDATE or DELETE'd. my statement -did- have the advantage of
being fast, at
2010/2/28 John R Pierce
> Terry wrote:
>
>> Hello,
>>
>> I am looking for a way to copy all the data from one table to another
>> on a regular basis, every 5 minutes let's say.
>>
>> INSERT INTO table2 SELECT * FROM table1;
>>
>> The above will copy all the data as is and insert it into the other
On Sun, 28 Feb 2010 15:56:41 -0600, Terry wrote about [GENERAL]
continuous copy/update one table to another:
>Hello,
>
>I am looking for a way to copy all the data from one table to another
>on a regular basis, every 5 minutes let's say.
>
>INSERT INTO table2 SELECT * FROM table1;
>
>The above wil
Terry wrote:
Hello,
I am looking for a way to copy all the data from one table to another
on a regular basis, every 5 minutes let's say.
INSERT INTO table2 SELECT * FROM table1;
The above will copy all the data as is and insert it into the other
table. What happens if I rerun it again? Will
Hello,
I am looking for a way to copy all the data from one table to another
on a regular basis, every 5 minutes let's say.
INSERT INTO table2 SELECT * FROM table1;
The above will copy all the data as is and insert it into the other
table. What happens if I rerun it again? Will it just append
rihad writes:
> I want the effects of the above foo.key in every sense, but only for
> entries having foo.flag=true. So I think I'll write before-statement
> triggers to do just that instead of the key. But is data consistency
> still guaranteed as the foreign key in foo would otherwise do?
No
rihad wrote:
Due to lack of support for partial (conditional) multi-column foreign
keys in 8.3, can before-triggers be used to implement them in terms of
data consistency and speed?
Let me clarify the question in semi-pseudo-SQL:
table foo {
bar_id int not null;
baz_id int not null;
fla
John Gage writes:
> 1) EFN=# \o aatest01.txt \i ./TestQuery01.txt
> 2) EFN=# \i ./TestQuery01.txt
> After I execute line 1), the results of the two queries contained in the
> TestQuery01.txt file can be found in aatest01.txt. Good. Excellent.
> However, line 2) results in no output to any place
On Sun, Feb 28, 2010 at 10:12 PM, John Gage wrote:
> This is a series of commands I issued to psql:
>
> 1) EFN=# \o aatest01.txt \i ./TestQuery01.txt
> 2) EFN=# \i ./TestQuery01.txt
> 3) EFN=# \p
> 4) select * from vocabulary_sources
> ;
> 5) EFN=# \g
> 6) EFN=# \p
> 7) select * from vocabulary_s
This is a series of commands I issued to psql:
1) EFN=# \o aatest01.txt \i ./TestQuery01.txt
2) EFN=# \i ./TestQuery01.txt
3) EFN=# \p
4) select * from vocabulary_sources
;
5) EFN=# \g
6) EFN=# \p
7) select * from vocabulary_sources
;
8) EFN=# \echo yes man
9) yes man
I have numbered the lines fo
"Ed L." writes:
> (gdb) bt
> #0 0x00346f8c43a0 in __read_nocancel () from /lib64/libc.so.6
> #1 0x00346f86c747 in _IO_new_file_underflow () from /lib64/libc.so.6
> #2 0x00346f86d10e in _IO_default_uflow_internal () from /lib64/libc.so.6
> #3 0x00346f8689cb in getc () from /lib6
Just for clarity: In the documentation
(http://www.postgresql.org/docs/8.4/static/functions-matching.html#FUNCTIONS-POSIX-REGEXP)
is mentioned "Flag g causes the function to find each match in the
string, not only the first one, and return a row for each such match. "
So in your example it was only
I didn't see an answer to this, so I thought I'd point out that you do
not need to do anything with XLOG to make a functional index. It is
only necessary when you want to make it crash-safe or work over SR.
But when you're building a new index type, making it crash safe is one
of the last things o
I found not only WAL writer process write data to WAL log files ,but
also write process which I thought only write dirty buffer to data
file .
Could some body tell me the reason?Tks a lot !!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscriptio
21 matches
Mail list logo
