Re: [ADMIN] Shared memory corrupted?
On Thu, 30 Oct 2003, Jeff Boes wrote: JB> We are experiencing the following error, usually during our nightly JB> delete-and-vacuum cycle (when there are very few other connections to JB> the database): JB> JB> 2003-10-30 01:36:59 [25392] LOG: server process (pid 697) was JB> terminated by signal 14 JB> 2003-10-30 01:36:59 [25392] LOG: terminating any other active server JB> processes JB> 2003-10-30 01:37:01 [1977] FATAL: The database system is in recovery mode JB> 2003-10-30 01:37:08 [25392] LOG: all server processes terminated; JB> reinitializing shared memory and semaphores JB> 2003-10-30 01:37:09 [2856] FATAL: The database system is starting up JB> 2003-10-30 01:37:09 [2855] LOG: database system was interrupted at JB> 2003-10-30 01:26:13 EST JB> JB> The only clues we have are that the server processes interrupted by JB> "signal 14" *seem* to be backends connected to Apache processes (on JB> another server). But even that isn't certain, because of the difficulty JB> in tracking down which process was doing what at the time. Signal 14 is SIGALRM. Some kind of badly-behaving watchdog? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [ADMIN] Column References
On Fri, Oct 31, 2003 at 13:44:40 -0600, "Epps, Aaron M." <[EMAIL PROTECTED]> wrote: > I've got a question about references, is it possible to specify criteria for the > Reference. For example, Table 1 has Field1 That References Field1 in Table2, > However I only want Field 1 in Table 1 to reference the Records in Table2 that have > the Valid Field set to TRUE. In other words, I don't want the user to be able to > enter invalid records from table 2 into field 1 in table 1. Is there a different > way of accomplishing the same thing? The way I have done this is to use redundant data in table1. For example in your case you might include a Valid field in table 1 with a constraint forcing it to always be true. Then you can use a two column foreign key reference from table 1 to table 2 that will enforce your constraint. (You will also need to make a unique index on the two column combination in table2.) ---(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 to the mailing list cleanly
