Hello,
I'm having trouble with postgres filling the log with SSL SYSCALL error: A
blocking operation was interrupted by a call to WSACancelBlockingCall. I've
googled search this error but came up with mostly 2 year old questions and
no answers. Can anyone help or point in the right direction to
On 29 Kwi, 17:16, [EMAIL PROTECTED] (Erik Jones) wrote:
On Apr 29, 2008, at 3:20 AM, wstrzalka wrote:
What is the full pg_standby command string (restore_command=) in
your recovery.conf. It sound's like you have pg_standby set to
delete
archived WALs and possibly have that a
Hi, I'm having a problem trying to write a query using join, and I hope
you can give me a hint.
suppose you have a three tables like these:
create table first_table (
id serial primary key,
description1 text);
create table second_table (
id serial primary key,
Hello All.
Now I try to link dll with MinGW from Example in Postgres Help.
Linker show me this error:
D:\users\anthony\kursor\abzcrm\c\foogcc -shared foo.o -o foo.dll -L
d:/files/local/PostgreSQL/8.3/lib -l postgres
Cannot export ⌂postgres_NULL_THUNK_DATA: symbol not found
collect2: ld returned
Gurjeet Singh wrote:
One of the advantages
of breaking up your data into partitions, as professed by Simon (I think)
(and I agree), is that you have smaller indexes, which improve performance.
And maybe having one huge index managing the uniqueness across partitioned
data just defeats the idea
vyang [EMAIL PROTECTED] writes:
I'm having trouble with postgres filling the log with SSL SYSCALL error: A
blocking operation was interrupted by a call to WSACancelBlockingCall.
That was fixed some time ago:
2007-05-17 21:20 tgl
* src/backend/libpq/: be-secure.c (REL7_4_STABLE),
2008/5/1 Ottavio Campana [EMAIL PROTECTED]:
Hi, I'm having a problem trying to write a query using join, and I hope you
can give me a hint.
suppose you have a three tables like these:
create table first_table (
id serial primary key,
description1 text);
create table
On Wed, Apr 30, 2008 at 12:36 PM, [EMAIL PROTECTED] wrote:
In this case, Postgres had been started in the foreground on a
terminal, so I went to that terminal, and did a ctrl-c. Eventually,
postgres stopped, but the terminal wouldn't respond either - and I had
to close it.
Just out
Is it possible to perform a text search with tables A--B returning A for
matches in B?
What I want to do is to be able take columns from both A and B and perform a
search based on the keywords entered by the user that matches A, B, or both
but always returns A.
Can this be done?
Thanks,
-Mont
On Thu, May 1, 2008 at 9:38 AM, Dan Armbrust
[EMAIL PROTECTED] wrote:
On Wed, Apr 30, 2008 at 12:36 PM, [EMAIL PROTECTED] wrote:
In this case, Postgres had been started in the foreground on a
terminal, so I went to that terminal, and did a ctrl-c. Eventually,
postgres stopped, but
I found a way to do this but I don't know if there is a better way.
What I did was to create a separate index on each table and construct a
query like:
SELECT * FROM a WHERE (to_tsvector(...) @@ to_tsquery(...)) OR primaryKey IN
(SELECT distinct(foreign_key) FROM b WHERE to_tsvector(...) @@
On Thursday 01 May 2008 01:30, Greg Smith wrote:
On Wed, 30 Apr 2008, Robert Treat wrote:
Whenever anyone posts a problem on 7.3, the first thing people do now
days is jump up and down waving thier arms about while exclaiming how
quickly they should upgrade. While I am certain there are
On Wednesday 30 April 2008 11:00, Craig Ringer wrote:
Robert Treat wrote:
If one were to have built something on postgresql 5 years ago, they would
have had to do it on 7.3. Whenever anyone posts a problem on 7.3, the
first thing people do now days is jump up and down waving thier arms
Robert Treat [EMAIL PROTECTED] writes:
This all sounds nice, but I don't see any movement from the project to
increase community commitment to 5 years for any release, so I think it's all
moot.
Movement? We did in fact support 7.3 for five years. Other than the
special case of deciding to
Robert Treat [EMAIL PROTECTED] writes:
And again, if you do the math, any install before 2008-11-17 would have been
on 7.3, which is less than 5 years.
I'm not sure how you're doing the math, but my copy of the release notes
dates 7.3 as 2002-11-27 and 7.3.21 as 2008-01-07, which makes it five
Osvaldo Kussama ha scritto:
To further explain, the following query selects both the rows from the join
where id_ref_first_tab has the desired value and default_value = true, while
I want to select the row corresponding to default_value = true only in case
no row corresponding to
Tom Lane wrote:
vyang [EMAIL PROTECTED] writes:
I'm having trouble with postgres filling the log with SSL SYSCALL error: A
blocking operation was interrupted by a call to WSACancelBlockingCall.
That was fixed some time ago:
2007-05-17 21:20 tgl
* src/backend/libpq/: be-secure.c
2008/5/1 Ottavio Campana [EMAIL PROTECTED]:
Osvaldo Kussama ha scritto:
To further explain, the following query selects both the rows from the
join
where id_ref_first_tab has the desired value and default_value = true,
while
I want to select the row corresponding to default_value
Because people can be smarter about the data partitioning.
Consider a table of users. Some are active, most are not. The active
users account for nearly all of the users table access, but I still
(occasionally) want to access info about the inactive users.
Partitioning users into active_users and
On Thursday 01 May 2008 13:40, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
And again, if you do the math, any install before 2008-11-17 would have
been on 7.3, which is less than 5 years.
I'm not sure how you're doing the math, but my copy of the release notes
dates 7.3 as
Nathan Boley wrote:
Because people can be smarter about the data partitioning.
Consider a table of users. Some are active, most are not. The active
users account for nearly all of the users table access, but I still
(occasionally) want to access info about the inactive users.
Partitioning users
Nathan Boley [EMAIL PROTECTED] writes:
Because people can be smarter about the data partitioning.
Consider a table of users. Some are active, most are not. The active
users account for nearly all of the users table access, but I still
(occasionally) want to access info about the inactive
Robert Treat [EMAIL PROTECTED] writes:
On Thursday 01 May 2008 13:40, Tom Lane wrote:
I'm not sure how you're doing the math, but my copy of the release notes
dates 7.3 as 2002-11-27 and 7.3.21 as 2008-01-07, which makes it five
years plus that we provided bug-fix releases for 7.3.
The whole
[EMAIL PROTECTED] (Robert Treat) writes:
On Thursday 01 May 2008 13:40, Tom Lane wrote:
7.4 was released 2003-11-17, so I think that it will very likely get
obsoleted at the end of 2008.
If that's the case, it'd be nice to get an official statement of that now. :-)
People have been making
An implementation of clustering without locking would start by comparing the
index to the table from the beginning to find the first mismatch. Rows
before the mismatch are fine, and can be left alone. From here on, go
through the index and rewrite each row in order. This will put the rows at
I am having trouble revoking a user's create privilege on
schema public.
Here is the sequence of commands that demonstrates the problem:
[EMAIL PROTECTED]:~$ su
Password:
saturn:/home/jdietrch# su postgres
[EMAIL PROTECTED]:/home/jdietrch$ psql
Welcome to psql 8.3.1, the PostgreSQL interactive
James Dietrich [EMAIL PROTECTED] writes:
Why does user2 still have create privilege on schema public?
You revoked that privilege in database postgres, which has little to
do with its state in any other database (and certainly not in template1
which is what you cloned to make db1).
On Thu, May 1, 2008 at 3:57 PM, Chris Browne [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Robert Treat) writes:
On Thursday 01 May 2008 13:40, Tom Lane wrote:
7.4 was released 2003-11-17, so I think that it will very likely get
obsoleted at the end of 2008.
If that's the case, it'd
Maybe I'm some crazy, radical DBA, but I've never had a version of
pgsql get EOLed out from underneath me. I migrated from 7.4 to 8.1
right around the time 8.2 came out then upgraded to 8.2 around 6
months later.
Where I work now we are looking at migrating from 8.1 to 8.2 or 8.3
Maybe I'm some crazy, radical DBA, but I've never had a version of
pgsql get EOLed out from underneath me.
Just for fun, I did a bit of digging in the release notes
http://developer.postgresql.org/pgdocs/postgres/release.html
and came up with this table about PG major releases and their
30 matches
Mail list logo
