Is there a bug listing for PostgreSQL somewhere?
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
I'm sure that "800 professionals" equates to something like 4
developers, 1 tester (part-time), 2 documentation specialist, and 792
marketing, sales, administration, legal staff and others required to
justify its cost, and 1 CEO who has his fingers into everything at MS.
Tim Allen wrote:
>Th
So... will current 7.1.1 databases upgrade without problems to 7.1.3?
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through t
I understand that the current port of Postgres for Windows requires the
cygwin package. I'd like to understand the requirement for cygwin,and
possibly try to port Postgres to run natively on Windows as a NT/2K
service. Anyone like to identify the challenges in such a port? Is it
at all poss
more efficient on Windows if it ran
without cygwin?
Three can you start cygwin programs on startup of the system?
mlw wrote:
>Dwayne Miller wrote:
>
>>I understand that the current port of Postgres for Windows requires the
>>cygwin package. I'd like to understand the req
seems like other systems keep very similar syntax to the CREATE TABLE
command. i.e.
ALTER TABLE blah ALTER COLUMN col datatype (precision.scale) NULL
ALTER TABLE blah ALTER COLUMN col datatype (precision.scale) NOT NULL
Dwayne
---(end of broadcast)--
I'm receiving duplicates of all posts from pg mailer. None of the other
lists I have seem to be affected. Any way I can check if my email is
duplicated in the subscription list?
Dwayne
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmast
I know that the MSSQL code works because the default collation sequence
for character fields is case-insensitive. You can change it for each
field independantly to be case sensitive, local specific, etc. I'm not
sure if PG supports a collation sequence attribute on column
definitions/indexes.
Not sure if this is the right place, but...
I am evaluating a move from FoxPro to PostgreSQL. So far, I like what I
see... alot. But, I have a data migration issue looming in the near
future that I need to address. The pgAdmin tool is nice, and works okay
on small databases, but I need to mig
Anyone know of any alternatives to using pgAdmin to migrate a database
(schema and data) from Foxpro to PostgreSQL? pgAdmin worked fine on my
initial test database, but it was slow... very slow. I'd like to try to
migrate one of our production databases, where several tables have
200,000+ record
What's the fastest way to select the number of rows in a table? If I
use count(*) with no whereclause, it uses a seq_scan and takes 4 secs
(122k rows). With a where clause, it uses an index and returns in < 1
sec. Selecting count(requestnumber), which is an indexed column, with
no where clause
requestnumber is an indexed field, was
suggested.
It's me and Postgres against another developer and MS SQL Server to see who
gets the port done fastest, with the best performance after the port. I don't
want to lose!
D
Doug McNaught wrote:
> "P. Dwayne Miller" <[EMAI
Where do I find out how to compile and run PostgreSQL under WindowsNT?
Thought I saw something about pre-built binaries available somewhere.
Thanks
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/sea
I recently upgraded to 7.1.3. I was experimenting with a script to
export data from FoxPro into an SQL file and multiple data files. The
SQL file creates the tables, indexes, foreign keys, etc, and calls the
COPY command to load the data from the appropriate data files.
It appears, and I cou
14 matches
Mail list logo
