I noticed that compiling with 5_1 patch applied fails due to
XLOG_archive_dir being removed from xlog.c , but
src/backend/commands/tablecmds.c still uses it.
I did the following to tablecmds.c :
5408c5408
< extern char XLOG_archive_dir[];
---
> extern char *XLogArchiv
On Wed, 2004-07-14 at 16:55, [EMAIL PROTECTED] wrote:
> On 14 Jul, Simon Riggs wrote:
> > PITR Patch v5_1 just posted has Point in Time Recovery working
> >
> > Still some rough edgesbut we really need some testers now to give
> > this a try and let me know what you think.
> >
> > Klaus N
Jodi Kanter wrote:
>Can field specific defaults easily be added to a table that is already
>in existence and has data in it? I cannot seem to locate the correct
>ALTER command in any of my books.
$ psql -c "\h alter table" | grep -iC 1 default
ALTER TABLE [ ONLY ] name [ * ]
ALTER [ COLUMN
Jodi Kanter wrote:
> Can field specific defaults easily be added to a table that is
> already in existence and has data in it? I cannot seem to locate the
> correct ALTER command in any of my books.
ALTER TABLE a ALTER COLUMN b SET DEFAULT c;
--
Peter Eisentraut
http://developer.postgresql.org/
On Wed, 2004-07-14 at 17:34, Jodi Kanter wrote:
> Can field specific defaults easily be added to a table that is already
> in existence and has data in it? I cannot seem to locate the correct
> ALTER command in any of my books.
ALTER TABLE table ALTER COLUMN column SET DEFAULT expression
--
Oli
Can field specific defaults easily be added to a table that is already
in existence and has data in it? I cannot seem to locate the correct
ALTER command in any of my books.
Thanks
Jodi
--
___
Jodi L Kanter
BioInformatics Da
On 14 Jul, Simon Riggs wrote:
> PITR Patch v5_1 just posted has Point in Time Recovery working
>
> Still some rough edgesbut we really need some testers now to give
> this a try and let me know what you think.
>
> Klaus Naumann and Mark Wong are the only [non-committers] to have tried
> t
On Wed, 14 Jul 2004, Joost Kraaijeveld wrote:
> Is it possible to turn of the case sensitivity for tables and columns in
> queries (to all CAPS)? I have a (closed source) tool that I have to use
> (Clarion) that generates the queries and I cannot change the way the
> tool generates the queries.
"Joost Kraaijeveld" <[EMAIL PROTECTED]> writes:
> I cannot see how Clarion creates the queries.
That's easily fixed. Turn on log_statement in postgresql's
configuration file and look at the server-side log to see what Clarion
is sending.
regards, tom lane
---
Simon Riggs <[EMAIL PROTECTED]> writes:
> I've not done power off tests, yet. They need to be done just to
> check...actually you don't need to do this to test PITR...
I agree, power off is not really the point here. What we need to check
into is (a) the mechanics of archiving WAL segments and (b
Hello,
I have written a windows tray application which starts postgres under windows.
Now I want to shutdown postgres, when windows shutdowns my tray-application. In this
case I cannot use the pg_ctl or other programs. If windows is in shutdown mode, it
does not allow to start a new program (li
Hi Peter,
Peter Eisentraut schreef:
> The table and column names are not actually case sensitive;
> they are just folded to lower case while you apparently expect upper case.
I am unsure of the translation of "fold". Is that the same as translate? Does that
mean that if Postgresql get a query wit
Am Mittwoch, 14. Juli 2004 10:55 schrieb Joost Kraaijeveld:
> Is it possible to turn of the case sensitivity for tables and columns in
> queries (to all CAPS)? I have a (closed source) tool that I have to use
> (Clarion) that generates the queries and I cannot change the way the tool
> generates t
Hi all,
Is it possible to turn of the case sensitivity for tables and columns in queries (to
all CAPS)? I have a (closed source) tool that I have to use (Clarion) that generates
the queries and I cannot change the way the tool generates the queries.
Groeten,
Joost Kraaijeveld
Askesis B.V.
Mol
On Wed, 2004-07-14 at 03:31, Christopher Kings-Lynne wrote:
> Can you give us some suggestions of what kind of stuff to test? Is
> there a way we can artificially kill the backend in all sorts of nasty
> spots to see if recovery works? Does kill -9 simulate a 'power off'?
>
I was hoping some
15 matches
Mail list logo
